[
https://issues.apache.org/jira/browse/CASSANDRA-3486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15344556#comment-15344556
]
Stefan Podkowinski commented on CASSANDRA-3486:
-----------------------------------------------
I've now looked at this issue as a potential use case for CASSANDRA-12016 and
added a test on top of it. The branch can be found at
[WIP-3486|https://github.com/spodkowinski/cassandra/tree/WIP-3486] and the test
I'm talking about in
[ActiveRepairServiceMessagingTest.java|https://github.com/spodkowinski/cassandra/blob/3a9ba2edcfe5a3a774089884d5fa7f4df4c9b70c/test/unit/org/apache/cassandra/service/ActiveRepairServiceMessagingTest.java].
My goal was to be able to make coordination between different nodes in repair
scenarios easier to test. The basic cases covered so far are pretty simple, but
I like to add more edge cases in the future. Nonetheless I wanted to share this
early on in case [~pauloricardomg] and others have any feedback on how this
approach would be helpful to make progress on this issue.
> 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)
