You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Ravi Prasad (JIRA)" <ji...@apache.org> on 2014/02/07 04:18:19 UTC

[jira] [Commented] (CASSANDRA-5921) Don't return empty list when the L0 compaction candidates could cause overlap in L1

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

Ravi Prasad commented on CASSANDRA-5921:
----------------------------------------

we're seeing overlaps in L1 in cassandra-2.0.4, multithreaded_compaction:false, concurrent_compactors:default(num_cores). Also reported by other user in ilist:
http://qnalist.com/questions/4702288/exception-during-add-node-due-to-test-beforeappend-on-sstablewriter

reverting the changes here to pre-2.0/CASSANDRA-5907, don't see any overlaps.
 

> Don't return empty list when the L0 compaction candidates could cause overlap in L1
> -----------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-5921
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5921
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Marcus Eriksson
>            Assignee: Marcus Eriksson
>            Priority: Minor
>             Fix For: 2.0.1
>
>         Attachments: 0001-instead-of-doing-no-compaction-if-we-have-sstables-t.patch, 0001-instead-of-doing-no-compaction-if-we-have-sstables-t.patch, 5921-v3.txt
>
>
> Followup to CASSANDRA-5907 - instead of returning empty list when the compaction candidates could cause overlap in L1, remove sstables that would cause the overlap from the candidates.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)