[
https://issues.apache.org/jira/browse/CASSANDRA-3486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14354836#comment-14354836
]
Jason Brown commented on CASSANDRA-3486:
----------------------------------------
It's been a while since I looked at this, but iirc, the problem was determining
if we should kill all ongoing repairs in a cluster, or expose a way for a user
to terminate a single one. The trick was 1) how to expose repair session ids to
users, globally, and 2) allows users to cancel an individual repair session
from any node in the cluster.
> 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: Jason Brown
> Priority: Minor
> Labels: repair
> Fix For: 2.1.4
>
> 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)
