cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Blake Eggleston (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-10446) Run repair with down replicas
Date Tue, 08 Nov 2016 19:40:59 GMT

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

Blake Eggleston commented on CASSANDRA-10446:
---------------------------------------------

In the {{--force}} case it doesn't because {{RepairMessageVerbHandler}} will apply the repairedAt
value computed at the beginning of the parent session, even if some nodes are being left out
of the repair.

In the normal case, CASSANDRA-6503 helps, but the inconsistency is still possible because
{{OnCompletionRunnable}} is run once a node has received all the files _it's_ expecting, but
not necessarily before other nodes involved in the repair have received all their data, and
there could still be a failure in that time.

> Run repair with down replicas
> -----------------------------
>
>                 Key: CASSANDRA-10446
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10446
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: sankalp kohli
>            Assignee: Blake Eggleston
>            Priority: Minor
>             Fix For: 4.0
>
>
> We should have an option of running repair when replicas are down. We can call it -force.



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

Mime
View raw message