Details
-
Improvement
-
Status: Resolved
-
Low
-
Resolution: Fixed
Description
Currently we manage a list of in-progress compactions in a system table, which we use to cleanup incomplete compactions when we're done. The problem with this is that 1) it's a bit clunky (and leaves us in positions where we can unnecessarily cleanup completed files, or conversely not cleanup files that have been superceded); and 2) it's only used for a regular compaction - no other compaction types are guarded in the same way, so can result in duplication if we fail before deleting the replacements.
I'd like to see each sstable store in its metadata its direct ancestors, and on startup we simply delete any sstables that occur in the union of all ancestor sets. This way as soon as we finish writing we're capable of cleaning up any leftovers, so we never get duplication. It's also much easier to reason about.
Attachments
Attachments
Issue Links
- breaks
-
CASSANDRA-10105 Windows dtest 3.0: TestOfflineTools failures
- Resolved
-
CASSANDRA-10109 Windows dtest 3.0: ttl_test.py failures
- Resolved
- contains
-
CASSANDRA-9854 Make CompactionController.maybeRefreshOverlaps public
- Resolved
- is related to
-
CASSANDRA-10006 2.1 format sstable filenames with "tmp" are not handled by 3.0
- Resolved
-
CASSANDRA-6756 Provide option to avoid loading orphan SSTables on startup
- Resolved
- relates to
-
CASSANDRA-10421 Potential issue with LogTransaction as it only checks in a single directory for files
- Resolved
-
CASSANDRA-9516 ViewTest.testSSTablesInBounds fails in trunk
- Resolved
-
CASSANDRA-10112 Refuse to start and print txn log information in case of disk corruption
- Resolved
-
CASSANDRA-8271 Remove SSTableDeletingTask
- Resolved
- links to