cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yuki Morishita (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-7124) Use JMX Notifications to Indicate Success/Failure of Long-Running Operations
Date Thu, 11 Dec 2014 15:25:13 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-7124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14242677#comment-14242677
] 

Yuki Morishita commented on CASSANDRA-7124:
-------------------------------------------

bq. 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? 

Yes. Trunk code will likely change often, so keeping your work in branch is preferable.

At this point, I think it will be more easier to work/review if we create sub tasks. Compaction
releated tasks(scrub, upgradesstable, compact, etc) and other tasks like move, decommission,
etc need to have different codes.
So why don't we focus on compaction related tasks first?

For the latter question above, I prefer keeping classes small and focus their own responsibility.
You can just go ahead and implement whatever you think is good.

> 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)

Mime
View raw message