[
https://issues.apache.org/jira/browse/CASSANDRA-10708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15005701#comment-15005701
]
Jeff Jirsa commented on CASSANDRA-10708:
----------------------------------------
Pending CI:
||2.1||2.2||trunk / 3.2 ? ||
| [branch|https://github.com/jeffjirsa/cassandra/tree/user_defined_cleanup-2.1]
| [branch|https://github.com/jeffjirsa/cassandra/tree/user_defined_cleanup-2.2]
| [branch|https://github.com/jeffjirsa/cassandra/tree/user_defined_cleanup] |
|
[testall|http://cassci.datastax.com/job/jeffjirsa-user_defined_cleanup-2.1-testall/lastBuild/]
|
[testall|http://cassci.datastax.com/job/jeffjirsa-user_defined_cleanup-2.2-testall/lastBuild/]
|
[testall|http://cassci.datastax.com/job/jeffjirsa-user_defined_cleanup-testall/lastBuild/]
|
> 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)
