[
https://issues.apache.org/jira/browse/CASSANDRA-3486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13178705#comment-13178705
]
Sylvain Lebresne commented on CASSANDRA-3486:
---------------------------------------------
I don't think we should close that ticket because I don't think that we have a
satisfying way to stop repair. A satisfying way to run repair would be to be
able to run 'nodetool repair stop <some_repair_session_id>' on the host the
repair was started on, on have it cleaning stop everything related to that
repair (including any validation or streaming going on) and this on every
participating nodes. That require a bit more work however and let me note that
I don't see this ticket as a priority at all.
> 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: Vijay
> Priority: Minor
> Labels: nodetool, repair, stop
> Fix For: 1.1
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
