cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Eriksson (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-8510) CompactionManager.submitMaximal may leak resources
Date Fri, 19 Dec 2014 07:12:14 GMT

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

Marcus Eriksson updated CASSANDRA-8510:
---------------------------------------
    Attachment: 0001-run-major-compactions-in-parallel.patch

patch to submit both tasks to the executor in parallel instead of sequentially

> 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
>             Fix For: 2.1.3
>
>         Attachments: 0001-run-major-compactions-in-parallel.patch
>
>
> 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)

Mime
View raw message