[
https://issues.apache.org/jira/browse/CASSANDRA-7124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14242492#comment-14242492
]
Rajanarayanan Thottuvaikkatumana commented on CASSANDRA-7124:
-------------------------------------------------------------
[~yukim], One question on the move operation. In the StorageService.java there
is a method {{private void move(Token newToken) throws IOException}} which
requires changes to return a ListenableFuture and for that we need to make the
logic of the above mentioned method as runnable, do submission and return the
ListenableFuture to its caller. Since it is not a runnable implementation,
should I go ahead and implement a class like
{{PendingRangeCalculatorService.java}} and implement a private static class
implementing Runnable and its corresponding run method in it? Or can I include
the logic of the {{private void move(Token newToken) throws IOException}}
method in any of the existing classes like
{{PendingRangeCalculatorService.java}}. Please confirm. 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)
