[ https://issues.apache.org/jira/browse/CASSANDRA-6912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13957521#comment-13957521 ]
Benedict commented on CASSANDRA-6912: ------------------------------------- I simply modified the deleting task back to schedule and dropped the deleteFile test, as this is really not necessary with this patch - I'll reintroduce it in CASSANDRA-6916, and possibly make CASSANDRA-6916 depend on CASSANDRA-6919 (which is the reason for moving all of these tasks into a scheduled operation). Possibly I'll then flatten the SSTableDeletingTask and this scheduled tidying up into one concept. The repository has been updated > SSTableReader.isReplaced does not allow for safe resource cleanup > ----------------------------------------------------------------- > > Key: CASSANDRA-6912 > URL: https://issues.apache.org/jira/browse/CASSANDRA-6912 > Project: Cassandra > Issue Type: Bug > Reporter: Benedict > Assignee: Benedict > Fix For: 2.1 beta2 > > > 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). -- This message was sent by Atlassian JIRA (v6.2#6252)