[ https://issues.apache.org/jira/browse/CASSANDRA-7124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14227058#comment-14227058 ]
Yuki Morishita commented on CASSANDRA-7124: ------------------------------------------- You can rename {{nextRepairCommand}} to be more generic, and using it across StorageService is fine. Other comments: - Don't create new ListeningExecutorService every time. Use CompactionExecutor. - If you do {{Future#get}} in async operation, it just blocks there. It ends up the same as sync method. > 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: cassandra-trunk-cleanup-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)