cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nick Bailey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-3486) Node Tool command to stop repair
Date Wed, 27 Apr 2016 16:10:13 GMT

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

Nick Bailey commented on CASSANDRA-3486:
----------------------------------------

bq. Do you think a blocking + timeout approach would be preferable?

Maybe. My goal in asking would be to know if the repair needs to be canceled on other nodes
or not. Right now you need to either just run the abort on all nodes from the start or run
it on the coordinator then check the participants to double check that it succeeded there
as well.

bq. I personally think we should go this route of making repair more stateful

I agree, especially with the upcoming coordinated repairs in C*

> Node Tool command to stop repair
> --------------------------------
>
>                 Key: CASSANDRA-3486
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3486
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Tools
>         Environment: JVM
>            Reporter: Vijay
>            Assignee: Paulo Motta
>            Priority: Minor
>              Labels: repair
>             Fix For: 2.1.x
>
>         Attachments: 0001-stop-repair-3583.patch
>
>
> After CASSANDRA-1740, If the validation compaction is stopped then the repair will hang.
This ticket will allow users to kill the original repair.



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

Mime
View raw message