Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Thu, 20 Dec 2012 19:35:13 +0000 (UTC)
From: "Radim Kolar (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12614461.1351820528011.38125.1356032113235@arcas>
In-Reply-To: <JIRA.12614461.1351820528011@arcas>
References: <JIRA.12614461.1351820528011@arcas>
Subject: [jira] [Commented] (CASSANDRA-4897) Allow tiered compaction define
 max sstable size
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ 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