[
https://issues.apache.org/jira/browse/CASSANDRA-11461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15219907#comment-15219907
]
Nick Bailey commented on CASSANDRA-11461:
-----------------------------------------
Well that depends. It starts by doing everything synchronously and tries to
calculate throughput. Based on the throughput it calculates it may try to run
things in parallel if it think it's required to complete but it prefers to run
a single repair at a time. I'm not 100% certain, but I believe in the case
where this was scene, OpsCenter was not running anything in parallel.
> Failed incremental repairs never cleared from pending list
> ----------------------------------------------------------
>
> Key: CASSANDRA-11461
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11461
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Adam Hattrell
>
> Set up a test cluster with 2 DC's, heavy use of LCS (not sure if that's
> relevant).
> Kick off cassandra-stress against it.
> Kick of an automated incremental repair cycle.
> After a bit a node starts flapping which causes a few repairs to fail. This
> is never cleared out of pending repairs - given the keyspace is replicated to
> all nodes it means they all have pending repairs that will never complete.
> Repairs are basically blocked at this point.
> Given we're using Incremental repairs you're now spammed with:
> "Cannot start multiple repair sessions over the same sstables"
> Cluster and logs are still available for review - message me for details.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
