You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jeff Jirsa (JIRA)" <ji...@apache.org> on 2015/11/14 23:29:10 UTC

[jira] [Updated] (CASSANDRA-10708) Add forceUserDefinedCleanup to allow more flexible cleanup for operators

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

Jeff Jirsa updated CASSANDRA-10708:
-----------------------------------
    Fix Version/s:     (was: 3.2)
                       (was: 2.2.x)
                       (was: 2.1.x)

> Add forceUserDefinedCleanup to allow more flexible cleanup for operators
> ------------------------------------------------------------------------
>
>                 Key: CASSANDRA-10708
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10708
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Jeff Jirsa
>            Assignee: Jeff Jirsa
>            Priority: Minor
>
> {{nodetool cleanup}} currently executes in parallel on all sstables in a table.  No source sstables are GCd until the parallel operation completes. In certain scenarios, this is nonideal (it has both memory and disk usage implications for operators who try to run the operation on larger tables). 
> Adding {{forceUserDefinedCleanup}} puts cleanup operations closer to parity with compaction {{forceUserDefinedCompaction}} for the rare cases where operators need to do something slightly different than the traditional cleanup. 



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