[ https://issues.apache.org/jira/browse/CASSANDRA-10422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14981146#comment-14981146 ]
Marcus Eriksson commented on CASSANDRA-10422: --------------------------------------------- Just had a very quick look, in 2.2+ we do incremental repair by default (and we also anticompact after full repairs) so we need to tell the other nodes whether this is a 'global' repair or not: https://github.com/apache/cassandra/blob/cassandra-2.2/src/java/org/apache/cassandra/repair/messages/PrepareMessage.java#L45 > 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: 2.1.x, 2.2.x, 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)