cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CASSANDRA-2405) should expose 'time since last successful repair' for easier aes monitoring
Date Fri, 02 Aug 2013 04:05:50 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-2405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jonathan Ellis resolved CASSANDRA-2405.
---------------------------------------

       Resolution: Duplicate
    Fix Version/s:     (was: 2.0.1)
         Assignee:     (was: Sylvain Lebresne)

Created CASSANDRA-5839 to pick this up again.  I think there's enough baggage here (discussion
of supercolumns, DCT) that it's worth starting fresh.
                
> 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
>         Attachments: CASSANDRA-2405.patch, CASSANDRA-2405-v2.patch, CASSANDRA-2405-v3.patch,
CASSANDRA-2405-v4.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.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message