[
https://issues.apache.org/jira/browse/CASSANDRA-7124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14205273#comment-14205273
]
Rajanarayanan Thottuvaikkatumana commented on CASSANDRA-7124:
-------------------------------------------------------------
[~thobbs] I have done the first cut of changes for the JMX notifications for
the "cleanup" command. Here are the things I have done
1) Implemented an abstract Runner class
2) Inherited the CleanupRunner from Runner and implemented the "run" method
specific to the "cleanup"
3) In the NodeProbe.java class implemented a cleanupAsync method with the JMX
related changes
4) In the NodeTool.java, the newly added method is called
I have done the clean compilation and other sanity tests related to the
changes. How do I test it, should you want to have a look at the changes done?
In that case should I upload a temporary patch? Please let me know. Thanks
> 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)
