You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2014/12/18 14:47:13 UTC

[jira] [Assigned] (CASSANDRA-8510) CompactionManager.submitMaximal may leak resources

     [ https://issues.apache.org/jira/browse/CASSANDRA-8510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis reassigned CASSANDRA-8510:
-----------------------------------------

    Assignee: Marcus Eriksson

> CompactionManager.submitMaximal may leak resources
> --------------------------------------------------
>
>                 Key: CASSANDRA-8510
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8510
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Benedict
>            Assignee: Marcus Eriksson
>
> Once an AbstractCompactionTask is created it MUST be executed for its resources to be cleaned up, however here a collection of AbstractCompactionTask are constructed; if any of them yield an exception the remainder will not be executed and their resources leaked. Somebody with experience of compaction should decide how best to deal with this: either release the resources manually on an exception or always execute each task.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)