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] [Updated] (CASSANDRA-4767) Need some indication of node repair success or failure
Date Mon, 07 Jan 2013 20:22:12 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-4767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Yuki Morishita updated CASSANDRA-4767:
--------------------------------------

    Attachment: 4767-1.2-v3.txt
                4767-1.1-v3.txt

Attaching v3 with the fix to only output the log it invoked.
I also attached 1.2 version of the patch separately, since it includes some refactoring around
repair code in StorageService.

bq. Do you mean what is logged?

yes.
                
> 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
>            Priority: Minor
>              Labels: jmx
>             Fix For: 1.1.9
>
>         Attachments: 4767-1.1.txt, 4767-1.1-v2.txt, 4767-1.1-v3.txt, 4767-1.2-v3.txt
>
>
> 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