Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Alternate method of ensuring no compacted SSTables left at startup #523

Merged

Conversation

wi11dey
Copy link
Contributor

@wi11dey wi11dey commented Aug 20, 2024

ColumnFamilyStore.removeUnfinishedCompactionLeftovers removes any SSTables that are part of another SSTable's compaction ancestors on startup. The reason this didn't help #521 is because it only runs when there are pending compactions on a given ks.cf, which isn't the case if you're just holding a ref post-successful-compaction. This PR changes startup code so that removeUnfinishedCompactionLeftovers runs on every ks.cf unconditionally

Functionally, the only changes are removeUnfinishedCompactionLeftovers is run in more cases than it was previously. It is always safe to run since it will only delete SSTables that are positively listed as an ancestor of another sstable

@wi11dey wi11dey force-pushed the wdey/alternate-scrub-obsolete-sstable branch from 083bcea to 946e6b6 Compare August 20, 2024 02:37
@rhuffy rhuffy merged commit 3cc5694 into palantir-cassandra-2.2.18 Aug 23, 2024
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants