[
https://issues.apache.org/jira/browse/CASSANDRA-3486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13624146#comment-13624146
]
Robert Coli commented on CASSANDRA-3486:
----------------------------------------
Regarding the priority of this ticket, operators frequently report hung repair
streaming sessions on #cassandra/cassandra-user@. Currently the only thing we
can tell them is to restart all affected nodes. This presumably gives them a
bad impression of cassandra. First, because the repair (which they have to run
once every GCGraceSeconds per best practice) hangs with no useful messaging.
Second, because the only solution is to restart multiple nodes. It's a little
bit surprising that this ticket suggests that this negative user experience is
uncommon enough to not expose some version of this functionality via nodetool..
two people's clusters have been in this state in #cassandra so far today and
it's only 2pm...
> 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: 2.0
>
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
