[
https://issues.apache.org/jira/browse/CASSANDRA-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156624#comment-13156624
]
Sylvain Lebresne commented on CASSANDRA-1740:
---------------------------------------------
I don't understand. Did you actually try v4 and got an exception in the log?
actualException is already the cause of the ExecutionException, so it is
directly the UserInterruptedException, unless that latter gets further
encapsulated by another exception but I see nowhere in the code where that
could happen. And as a matter of fact, if you do try stopping a compaction,
both v3 and v5 do log an error, while v4 does not. If your testing differs,
there is something going on.
> Nodetool commands to query and stop compaction, repair, cleanup and scrub
> -------------------------------------------------------------------------
>
> Key: CASSANDRA-1740
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1740
> Project: Cassandra
> Issue Type: Improvement
> Components: Tools
> Reporter: Chip Salzenberg
> Assignee: Vijay
> Priority: Minor
> Labels: compaction
> Fix For: 1.0.4
>
> Attachments: 0001-Patch-to-Stop-compactions-v2.patch,
> 0001-Patch-to-Stop-compactions-v3.patch,
> 0001-Patch-to-Stop-compactions-v4.patch,
> 0001-Patch-to-Stop-compactions-v5.patch,
> 0001-Patch-to-Stop-compactions.patch, CASSANDRA-1740.patch
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> The only way to stop compaction, repair, cleanup, or scrub in progress is to
> stop and restart the entire Cassandra server. Please provide nodetool
> commands to query whether such things are running, and stop them if they are.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
