cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Eriksson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-11461) Failed incremental repairs never cleared from pending list
Date Thu, 31 Mar 2016 15:24:25 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-11461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15220026#comment-15220026
] 

Marcus Eriksson commented on CASSANDRA-11461:
---------------------------------------------

[~nickmbailey] with CASSANDRA-11451 users can run repair service just like today, only it
doesn't make much sense to support incremental repairs in repair service as we never anticompact
with sub range 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)

Mime
View raw message