[
https://issues.apache.org/jira/browse/CASSANDRA-4767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis updated CASSANDRA-4767:
--------------------------------------
Component/s: Tools
Affects Version/s: (was: 1.1.4)
Fix Version/s: 1.2.0
1.1.7
Assignee: Yuki Morishita
Labels: jmx (was: )
Yes, JMX is the right place for this.
One possible API: a List of Map<String: String>:
{'Session': session id,
'Initiator': node "coordinating" the repair,
'Status': 'Pending'|'Validating'|'Repairing'|'Success'|'Failed',
'Started': start timestamp,
'Finished': finish timestamp}
If this is unintrusive enough we can try to get it into 1.1.x; otherwise, an
early 1.2 release.
/cc [~j.casares]
> 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
