cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jon Hermes (JIRA)" <j...@apache.org>
Subject [jira] Issue Comment Edited: (CASSANDRA-1811) Cleanup smallest CFs first
Date Sat, 04 Dec 2010 00:58:11 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12966751#action_12966751
] 

Jon Hermes edited comment on CASSANDRA-1811 at 12/3/10 7:56 PM:
----------------------------------------------------------------

-This may need to be rebased if 1812 is committed first and vice-versa.-
-Oh well.-
Nope, both apply cleanly. Hurrah!

      was (Author: jhermes):
    This may need to be rebased if 1812 is committed first and vice-versa.
Oh well.
  
> Cleanup smallest CFs first
> --------------------------
>
>                 Key: CASSANDRA-1811
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1811
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 0.6.8
>            Reporter: Paul Querna
>            Assignee: Jon Hermes
>            Priority: Minor
>             Fix For: 0.6.9
>
>         Attachments: 1811.txt
>
>
> 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.


Mime
View raw message