[
https://issues.apache.org/jira/browse/CASSANDRA-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13021595#comment-13021595
]
Hudson commented on CASSANDRA-2290:
-----------------------------------
Integrated in Cassandra-0.7 #447 (See
[https://hudson.apache.org/hudson/job/Cassandra-0.7/447/])
> Repair hangs if one of the neighbor is dead
> -------------------------------------------
>
> Key: CASSANDRA-2290
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2290
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.6
> Reporter: Sylvain Lebresne
> Assignee: Sylvain Lebresne
> Priority: Minor
> Fix For: 0.7.5, 0.8
>
> Attachments: 0001-Don-t-start-repair-if-a-neighbor-is-dead.patch
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> Repair don't cope well with dead/dying neighbors. There is 2 problems:
> # Repair don't check if a node is dead before sending a TreeRequest; this
> is easily fixable.
> # If a neighbor dies mid-repair, the repair will also hang forever.
> The second point is not easy to deal with. The best approach is probably
> CASSANDRA-1740 however. That is, if we add a way to query the state of a
> repair, and that this query correctly check all neighbors and also add a way
> to cancel a repair, this would probably be enough.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
