cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Eriksson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-10422) Avoid anticompaction when doing subrange repair
Date Tue, 10 Nov 2015 17:26:11 GMT

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

Marcus Eriksson commented on CASSANDRA-10422:
---------------------------------------------

bq. do I even want to bother with preventing them from requesting subrange repair with incremental
repair 
No, I think we can just skip anticompaction in this case. Maybe output a warning?

bq. For 2.1 it's sufficient to prevent them from requesting the problem combination?
yes

> Avoid anticompaction when doing subrange repair
> -----------------------------------------------
>
>                 Key: CASSANDRA-10422
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10422
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Marcus Eriksson
>            Assignee: Ariel Weisberg
>             Fix For: 3.1, 2.1.x, 2.2.x
>
>
> 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)

Mime
View raw message