Details
-
Task
-
Status: Open
-
Normal
-
Resolution: Unresolved
-
None
-
None
Description
There are instances where SSTable references are not guaranteed to be released (e.g. CompactionTask.runWith) because there is no try/finally around the reference acquire/release. We should audit all places where SSTable references are acquired and wrap them appropriately. Leaked references cause junk files to build up on disk and on a restart can lead to data resurrection.
Attachments
Issue Links
- relates to
-
CASSANDRA-8829 Add extra checks to catch SSTable ref counting bugs
- Resolved