[
https://issues.apache.org/jira/browse/CASSANDRA-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13018315#comment-13018315
]
Sylvain Lebresne commented on CASSANDRA-1740:
---------------------------------------------
As for handling the multi-threaded compactions, the hashcode would more or less
work but since it's not totally safe I would prefer assigning a name to each
compaction which could be:
* a uuid assigned to each compaction when created
* a simple (atomically) increasing number
* a simple (atomically) increasing number for each type of compaction, the
name being something like major-42 or minor-3012. Nice thing is it tells you
how many minor, major, validata, ... compaction you have run already.
> 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: Pavel Yaskevich
> Priority: Minor
> Fix For: 0.7.5
>
> Attachments: 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
