[
https://issues.apache.org/jira/browse/CASSANDRA-7124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14196431#comment-14196431
]
Tyler Hobbs commented on CASSANDRA-7124:
----------------------------------------
bq. 1) Which are the Fix Versions for this issue?
Let's do 3.0 (the trunk branch). It would be bad to break nodetool operations
in a patch release for a nice-to-have feature.
bq. I was looking at the patches given for CASSANDRA-4767 and found that some
of the classes used in the 1.2 version are not available in the 2.1 version
such as "src/java/org/apache/cassandra/service/AntiEntropyService.java"
Most of the changes will probably be in StorageService. The AntiEntropyService
class is specific to repairs.
> Use JMX Notifications to Indicate Success/Failure of Long-Running Operations
> ----------------------------------------------------------------------------
>
> Key: CASSANDRA-7124
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7124
> Project: Cassandra
> Issue Type: Improvement
> Components: Tools
> Reporter: Tyler Hobbs
> Assignee: Rajanarayanan Thottuvaikkatumana
> Priority: Minor
> Labels: lhf
> Fix For: 3.0
>
>
> If {{nodetool cleanup}} or some other long-running operation takes too long
> to complete, you'll see an error like the one in CASSANDRA-2126, so you can't
> tell if the operation completed successfully or not. CASSANDRA-4767 fixed
> this for repairs with JMX notifications. We should do something similar for
> nodetool cleanup, compact, decommission, move, relocate, etc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
