You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Marcus Eriksson (JIRA)" <ji...@apache.org> on 2015/11/17 10:23:11 UTC

[jira] [Resolved] (CASSANDRA-10422) Avoid anticompaction when doing subrange repair

     [ https://issues.apache.org/jira/browse/CASSANDRA-10422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marcus Eriksson resolved CASSANDRA-10422.
-----------------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: 2.2.x)
                       (was: 2.1.x)
                   2.2.4
                   2.1.12

+1, committed

also added a few dtests: https://github.com/riptano/cassandra-dtest/pull/664

> Avoid anticompaction when doing subrange repair
> -----------------------------------------------
>
>                 Key: CASSANDRA-10422
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10422
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Compaction
>            Reporter: Marcus Eriksson
>            Assignee: Ariel Weisberg
>             Fix For: 2.1.12, 2.2.4, 3.0.1, 3.1
>
>
> If we do split the owned range in say 1000 parts, and then do one repair each, we could potentially anticompact every sstable 1000 times (ie, we anticompact the repaired range out 1000 times). We should avoid anticompacting at all in these cases.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)