[
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.1-v2.txt
Attaching v2.
I made the following changes:
- Created RepairRunner that implements NotificationListener and it now only
handles notification from repair command that it invoked. Code could be cleaned
up further (for example, notification listener could be registered once) but I
needed to touch other commands(scrub, cleanup...) as well so I avoided to
change all the code.
- Notification source is now ObjectName. I think JMX serializes source object
and sends it to listener, so using ObjectName is the right thing. Thanks for
reminding.
- 'forceTableRapirAsync' -> 'forceRepairAsync'
I think we need to keep blocking repair methods for backward compatibility.
There could be someone using those directly from their scripts.
Speaking of backward compatibility, the patch modifies behavior of repair
command in the way that it outputs repair progress but I think it should not be
the concern to put this in 1.1 release.
> 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
>
>
> 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
