[
https://issues.apache.org/jira/browse/CASSANDRA-12489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15900209#comment-15900209
]
Kurt Greaves commented on CASSANDRA-12489:
------------------------------------------
Reaper supports incremental repairs as well, without splitting the ranges (or
at least that's what I'm led to believe). In which case it should just run
repairs so they don't occur at the same time. As Marcus says, incremental
repairs reduce the amount of data that needs to be repaired, while splitting on
the ranges still repairs all the data, but just in a more manageable fashion.
> consecutive repairs of same range always finds 'out of sync' in sane cluster
> ----------------------------------------------------------------------------
>
> Key: CASSANDRA-12489
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12489
> Project: Cassandra
> Issue Type: Bug
> Components: Streaming and Messaging
> Reporter: Benjamin Roth
> Assignee: Benjamin Roth
> Labels: lhf
> Attachments: trace_3_10.1.log.gz, trace_3_10.2.log.gz,
> trace_3_10.3.log.gz, trace_3_10.4.log.gz, trace_3_9.1.log.gz,
> trace_3_9.2.log.gz
>
>
> No matter how often or when I run the same subrange repair, it ALWAYS tells
> me that some ranges are our of sync. Tested in 3.9 + 3.10 (git trunk of
> 2016-08-17). The cluster is sane. All nodes are up, cluster is not overloaded.
> I guess this is not a desired behaviour. I'd expect that a repair does what
> it says and a consecutive repair shouldn't report "out of syncs" any more if
> the cluster is sane.
> Especially for tables with MVs that puts a lot of pressure during repair as
> ranges are repaired over and over again.
> See traces of different runs attached.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
