[
https://issues.apache.org/jira/browse/CASSANDRA-7932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14133155#comment-14133155
]
Benedict commented on CASSANDRA-7932:
-------------------------------------
I was mistaken. Whilst that patch fixes what appears to be a leak we could
encounter from the same code path, the actual leak was more involved. I've
patched on top of the leak detection code for trunk, however if we get a thumbs
up we can backport to 2.1
[Patch|https://github.com/belliottsmith/cassandra/tree/7932-corruptleak]
> Corrupt SSTable Cleanup Leak Resources
> --------------------------------------
>
> Key: CASSANDRA-7932
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7932
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Benedict
> Assignee: Benedict
> Fix For: 2.1.1
>
> Attachments: 7932.txt
>
>
> CASSANDRA-7705, during the BlackingListingCompactionsTest, detected leaks.
> I've tracked this down to DataTracker.removeUnreadableSSTables() , which does
> not release the reference to any sstables from the tracker.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
