[jira] [Comment Edited] (CASSANDRA-9097) Repeated incremental nodetool repair results in failed repairs due to running anticompaction

["Jeremiah Jordan (JIRA)" <ji...@apache.org>]

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

Jeremiah Jordan edited comment on CASSANDRA-9097 at 5/5/15 7:39 AM:
--------------------------------------------------------------------

It tests > not >=.  So maybe just rename so it reflects that.


was (Author: jjordan):
It tests > not >=.

> Repeated incremental nodetool repair results in failed repairs due to running anticompaction
> --------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-9097
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9097
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Gustav Munkby
>            Assignee: Yuki Morishita
>            Priority: Minor
>             Fix For: 2.1.x
>
>         Attachments: 0001-Wait-for-anticompaction-to-finish.patch
>
>
> I'm trying to synchronize incremental repairs over multiple nodes in a Cassandra cluster, and it does not seem to easily achievable.
> In principle, the process iterates through the nodes of the cluster and performs `nodetool -h $NODE repair --incremental`, but that sometimes fails on subsequent nodes. The reason for failing seems to be that the repair returns as soon as the repair and the _local_ anticompaction has completed, but does not guarantee that remote anticompactions are complete. If I subsequently try to issue another repair command, they fail to start (and terminate with failure after about one minute). It usually isn't a problem, as the local anticompaction typically involves as much (or more) data as the remote ones, but sometimes not.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)