You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Rajanarayanan Thottuvaikkatumana (JIRA)" <ji...@apache.org> on 2014/11/04 16:56:37 UTC
[jira] [Commented] (CASSANDRA-7124) Use JMX Notifications to
Indicate Success/Failure of Long-Running Operations
[ https://issues.apache.org/jira/browse/CASSANDRA-7124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14196272#comment-14196272 ]
Rajanarayanan Thottuvaikkatumana commented on CASSANDRA-7124:
-------------------------------------------------------------
[~thobbs],
1) Which are the Fix Versions for this issue?
2) 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". If I know the right fix versions, that will help me to look at the right code base.
> 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
> Priority: Minor
> Labels: lhf
>
> 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)