Description
There are a number of possible race conditions on resource cleanup from the use of cloneWithNewSummarySamplingLevel, because the replacement sstable can be itself replaced/obsoleted while the prior sstable is still referenced (this is actually quite easy with compaction, but can happen in other circumstances less commonly).
Attachments
Issue Links
- breaks
-
CASSANDRA-7000 Assertion in SSTableReader during repair.
- Resolved
- is depended upon by
-
CASSANDRA-6916 Preemptive opening of compaction result
- Resolved
-
CASSANDRA-6919 Use OpOrder to guard sstable references for reads, instead of acquiring/releasing references
- Resolved