cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rajanarayanan Thottuvaikkatumana (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-7124) Use JMX Notifications to Indicate Success/Failure of Long-Running Operations
Date Mon, 10 Nov 2014 20:24:35 GMT


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
3) In the class implemented a cleanupAsync method with the JMX related changes
4) In the, 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:
>             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

View raw message