[ https://issues.apache.org/jira/browse/CASSANDRA-7124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14267568#comment-14267568 ]
Rajanarayanan Thottuvaikkatumana commented on CASSANDRA-7124: ------------------------------------------------------------- [~yukim], Merged the code for cleanup with the commit - https://github.com/rnamboodiri/cassandra/commit/5ec552c326119cf573dd3b07344e88ad0f5d2449 I have run the test {{ant test -Dtest.name=CleanupTest}} and it is working fine. Also ran the cleanup command from the command line and looks good. 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 > > Attachments: 7124-wip.txt, cassandra-trunk-compact-7124.txt, > cassandra-trunk-decommission-7124.txt > > > 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)