cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nick Bailey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-4767) Need some indication of node repair success or failure
Date Tue, 06 Nov 2012 16:50:12 GMT

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

Nick Bailey commented on CASSANDRA-4767:
----------------------------------------

Our approach with these jmx type operations in the past has been let the jmx call block until
it finishes. That does have some downsides though like checking progress and jmx timeouts.

If we do this we should hopefully make it generic enough to hook all of our long running jmx
calls in to.
                
> Need some indication of node repair success or failure
> ------------------------------------------------------
>
>                 Key: CASSANDRA-4767
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4767
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Tools
>            Reporter: Ahmed Bashir
>            Assignee: Yuki Morishita
>              Labels: jmx
>             Fix For: 1.1.7, 1.2.0
>
>
> We are currently verifying node repair status via basic log analysis.  In order to automatically
track the status of periodic node repair jobs, it would be better to have an indicator (through
JMX perhaps).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message