cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benedict (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-7932) Corrupt SSTable Cleanup Leak Resources
Date Fri, 19 Sep 2014 16:43:38 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-7932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14140846#comment-14140846
] 

Benedict commented on CASSANDRA-7932:
-------------------------------------

[~jbellis] since yuki has suggested incorporating both into 2.1.1, what's your input? I'm
comfortable either way, but there are certainly advantages to stamping out resource leaks
earlier than later.

> 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
>
>
> 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)

Mime
View raw message