[jira] [Commented] (CASSANDRA-2834) Avoid repair getting started twice at the same time for the same CF

["Sylvain Lebresne (JIRA)" <ji...@apache.org>]

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

Sylvain Lebresne commented on CASSANDRA-2834:
---------------------------------------------

bq. It may seem like it is possible to start repair twice at the same time on the same CF?

It is possible. Right now the only cases where we abort a repair quickly is if some neighbors are dead.

Repairing twice on the same CF is indeed useless and we can try to avoid it. This is however not totally trivial because the two repairs can be started on different nodes so we'll have to synchronize somehow. Rather, it's not hard per se, but this will require some addition to the network protocol and is thus a little longer term that one could hope.

Note that this may be made simpler by CASSANDRA-1740 in that it would propose to have a way to abort a repair (which don't have so far).

> Avoid repair getting started twice at the same time for the same CF
> -------------------------------------------------------------------
>
>                 Key: CASSANDRA-2834
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2834
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Terje Marthinussen
>
> It may seem like it is possible to start repair twice at the same time on the same CF?
> Not 100% verified, but if this is indeed the case, we may want to consider avoiding that including making nodetool repair abort and return and error if repair is attempted on the same CF as one which already have repair running.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira