[
https://issues.apache.org/jira/browse/CASSANDRA-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12966706#action_12966706
]
Jon Hermes commented on CASSANDRA-1811:
---------------------------------------
bq. An alternative would be to extend forceclean in jmx to allow you to specify
both the Keyspace and a CF, so that you could manually do specific CFs.
This is resolved in CASSANDRA-1812, but there's value in both.
> Cleanup smallest CFs first
> --------------------------
>
> Key: CASSANDRA-1811
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1811
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Paul Querna
> Assignee: Jon Hermes
> Priority: Minor
> Fix For: 0.6.9
>
>
> When running a cleanup, it would be an advantage to anti-compact the smallest
> SSTables first, so that free disk space is gradually increased, so that
> larger sstables later on are more likely to successfully anti-compact.
> In 0.6, currently Table.forceCleanup() just iterates the list of CFs in
> whatever order they come from tableMetadata.getColumnFamilies, which is just
> a keySet().
> The code should be changed to sort the CFs, smallest first.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
