You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Nick Bailey (JIRA)" <ji...@apache.org> on 2016/04/01 20:02:25 UTC
[jira] [Commented] (CASSANDRA-11461) Failed incremental repairs
never cleared from pending list
[ https://issues.apache.org/jira/browse/CASSANDRA-11461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15222072#comment-15222072 ]
Nick Bailey commented on CASSANDRA-11461:
-----------------------------------------
Hmm ok so we should prevent full incremental repairs from ever running on more than one node and never allow subrange incremental repairs?
> 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)