[
https://issues.apache.org/jira/browse/CASSANDRA-7124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14242415#comment-14242415
]
Rajanarayanan Thottuvaikkatumana commented on CASSANDRA-7124:
-------------------------------------------------------------
[~yukim], Sure I can do that. Can you please explain the branching part a bit?
Did you mean to say that, get the latest version from trunk, create a branch
locally, apply all the changes and then push that to a different repository
such as to my own Github repository and share the link with you?
One other opinion is that, if you look at all these operations for which I am
making changes, all these changes are independent and implementations are
different. In other words, the changes for compact and decommission are two
totally different things and they can be committed separately. Just like the
way the original repair task was implemented earlier and committed separately.
Just because of that itself dealing with them independently will be ideal. More
over, if changes are there in all the implementations, verifying all of them
together and doing any changes after the review process will be more difficult
than dealing with them one by one. So if you can have a look at the patches
submitted one by one at your convenience, I think that will be easy for you and
me. Feel free to be opinionated and let me know. I will do it accordingly.
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)
