[
https://issues.apache.org/jira/browse/CASSANDRA-11461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15220014#comment-15220014
]
Nick Bailey commented on CASSANDRA-11461:
-----------------------------------------
We would need to reproduce the issue in OpsCenter with debug logging enabled to
see how many parallel repairs OpsCenter is attempting. But I could easily see
how you would hit this issue with vnodes enabled. We don't have any logic to
prevent that from happening.
> 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)
