[
https://issues.apache.org/jira/browse/CASSANDRA-4767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13531216#comment-13531216
]
Yuki Morishita commented on CASSANDRA-4767:
-------------------------------------------
So I've been working on this issue a while, and I think it is not useful to log
session state per repair session.
Repair session is generated per range, so when you invoke your repair command
without specifying keyspace and -pr option, the command will generate (number
of keyspaces) x (replication factor) x (number of tokens(for vnodes) sessions.
When vnode is enabled, the number could become a lot.
I think what we want here is to track repair state per invocation of repair
command. So what I'm working on right now is to give some feedback to
client(using JMX notification). In this way, we can go further and make repair
command 'async', so that we can get rid of JMX timeout(CASSANDRA-2126).
> 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.8
>
>
> 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
