[
https://issues.apache.org/jira/browse/CASSANDRA-6912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13957094#comment-13957094
]
Benedict commented on CASSANDRA-6912:
-------------------------------------
Dagnabit. Good catch - I originally had this bundled up with two other patches,
and in separating them I was apparently not as careful as I had thought. The
whole of tidy() was scheduled, and I thought I didn't need that after I
extracted this (for reasons I won't get into). I'll reintroduce it.
> 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)
