[
https://issues.apache.org/jira/browse/CASSANDRA-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13147232#comment-13147232
]
Vijay commented on CASSANDRA-1740:
----------------------------------
I can do all of the above, but i still think it is an Exception because
someone/something interrupted (agree about runtime exception and will add more
message so users wont panic). It will be easier to maintain later because
people dont need to understand a return vs exception, they just need to worry
about is an exception will be thrown somewhere.
I can remove the exception and just do return if stopped if we prefer
otherwise, let me know.
> 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.3
>
> Attachments: 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