cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Radim Kolar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-4897) Allow tiered compaction define max sstable size
Date Thu, 20 Dec 2012 19:35:13 GMT

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

Radim Kolar commented on CASSANDRA-4897:
----------------------------------------

You are right in both cases. There needs to be some kind of heuristics when to compact bucket
with max sized tables. I have to take a look at lucene code, but it has way more elaborated
tiered compaction (not bucket based).
                
> Allow tiered compaction define max sstable size
> -----------------------------------------------
>
>                 Key: CASSANDRA-4897
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4897
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Radim Kolar
>            Assignee: Radim Kolar
>             Fix For: 1.2.1
>
>         Attachments: cass-maxsize1.txt, cass-maxsize2.txt
>
>
> Lucene is doing same thing. Correctly configured max segment size will recycle old data
faster with less diskspace.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message