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 Tue, 09 Dec 2014 14:24:12 GMT


Rajanarayanan Thottuvaikkatumana commented on CASSANDRA-7124:

[~yukim], Please find attached the patch for the decommission task. There was no test case
for this and I have added one. Since this is a process of decommissioning one node from a
ring, I could not test this as I have only a single machine with me. Before applying this
patch, please apply the patch for the compact task I had attached earlier. The reason is that
there is one new class file creation happening in that patch ( Please let me
know if you have any comments. 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
>         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

View raw message