[
https://issues.apache.org/jira/browse/CASSANDRA-2405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13021005#comment-13021005
]
Peter Schuller commented on CASSANDRA-2405:
-------------------------------------------
IMO yes, since the aim was to make it easy to write a script. Poking JMX in a
shell script != easy unless you happen to have crossed that threshold already;
nodetool is one way to do that.
Also: From brief inspection it seems it's storing the time of the *completion*
of the last successful repair. It needs to store the time of the *commencement*
of the last successful repair in order to be useful for monitoring for gc grace
seconds purposes since that it what determines at what point in the timeline
the node is "guaranteed" to have seen writes.
> should expose 'time since last successful repair' for easier aes monitoring
> ---------------------------------------------------------------------------
>
> Key: CASSANDRA-2405
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2405
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Peter Schuller
> Assignee: Pavel Yaskevich
> Priority: Minor
> Fix For: 0.7.5
>
> Attachments: CASSANDRA-2405.patch
>
>
> The practical implementation issues of actually ensuring repair runs is
> somewhat of an undocumented/untreated issue.
> One hopefully low hanging fruit would be to at least expose the time since
> last successful repair for a particular column family, to make it easier to
> write a correct script to monitor for lack of repair in a non-buggy fashion.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
