[
https://issues.apache.org/jira/browse/CASSANDRA-10422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14980688#comment-14980688
]
Ariel Weisberg commented on CASSANDRA-10422:
--------------------------------------------
[~krummas] Is this as simple as having a repair that has a start/end token(s)
specified ignoring (or rejecting) the incremental repair flag? Say [here in
RepairOption.parse|https://github.com/apache/cassandra/blob/ef1b4c0f5a8e0677efd3ec25fa735782ce1b1480/src/java/org/apache/cassandra/repair/messages/RepairOption.java#L143]?
> 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)
