[ 
https://issues.apache.org/jira/browse/CASSANDRA-2405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13049784#comment-13049784
 ] 

Sylvain Lebresne commented on CASSANDRA-2405:
---------------------------------------------

I'm keen on adding persisted stats for repair for CASSANDRA-2698. Recording the 
start and end time of repair also amounts to persisting stats on repair. Given 
that, I don't care too much about what the description of this says, but I'm 
pretty much opposed to doing anything here that would make CASSANDRA-2698 much 
harder that it needs unless there is a good reason, and I don't see one. I'm 
happy with making this a duplicate or dependency of CASSANDRA-2698 though.

> 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
>          Components: Core
>            Reporter: Peter Schuller
>            Assignee: Pavel Yaskevich
>            Priority: Minor
>             Fix For: 0.8.1
>
>         Attachments: CASSANDRA-2405-v2.patch, CASSANDRA-2405-v3.patch, 
> 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

        

Reply via email to