[
https://issues.apache.org/jira/browse/CASSANDRA-3486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13178504#comment-13178504
]
Sylvain Lebresne commented on CASSANDRA-3486:
---------------------------------------------
As a said back on CASSANDRA-3316, I see forceTerminateAllRepairSessions more as
a band-aid solution to avoid having someone stuck until we better handle repair
failures and have a correct to stop it. But it isn't really a very use friendly
solution since it doesn't stop properly the repair (it won't stop the
validation compaction (though we can do that by other means now), nor any
streaming that would be running) and you have to run it everywhere. For all
those reason, my opinion is that we should keep this JMX only, I see no good
reason to promote it to nodetool. That's just an opinion though.
> 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
