[
https://issues.apache.org/jira/browse/CASSANDRA-3486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15258764#comment-15258764
]
Nick Bailey commented on CASSANDRA-3486:
----------------------------------------
Some questions:
* If the abort is initiated on the coordinator can we return the
success/failure of the attempt to abort on the participants as well? And vice
versa?
* Similarly for the list of results when aborting all jobs.
* Can we make sure we are testing the case where for whatever reason a
coordinator or participant receives an abort for a repair it doesn't know about?
* Since we are now tracking repairs by uuid like this, can we expose a progress
API outside of the jmx notification process? An mbean for retrieving the
progress/status of a repair job by uuid?
> 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)
