[
https://issues.apache.org/jira/browse/CASSANDRA-3486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15182995#comment-15182995
]
Paulo Motta commented on CASSANDRA-3486:
----------------------------------------
[~jasobrown] do you still plan to work on this? There is a lot of overlap
between this and CASSANDRA-11190, which I'll start working on it soon, so I
wanted to check if we could still reuse anything of your first draft or better
start from scratch.
As to your previous questions, I think we can provide a way for users to
stop/abort an ongoing local repair session given its session id. So, if session
<id> is happening on nodes A, B and C, I can execute {{nodetool repair --abort
<id>}} on nodes A, B or C to abort session <id>. I if execute {{nodetool repair
--abort <id>}} on node D, it will print something like {{No ongoing repair
session found with id <id>}}. For this to be useful, we should also provide a
{{nodetool repair --list}} command to list ongoing repair sessions on the local
node, and also {{nodetool repair --abort-all}} to abort all ongoing sessions on
the local node.
> 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.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)
