[
https://issues.apache.org/jira/browse/CASSANDRA-2405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13049882#comment-13049882
]
Sylvain Lebresne commented on CASSANDRA-2405:
---------------------------------------------
Hum, the thing is that there will be many repair sessions for a given set of
KS/CF and range. So you need one of the key (either row key or supercolumn
name) to be the session_id (or anything that is unique to a session). If you
use a row for each KS/CF pair and one super column for each session, you will
have one super column for each repair made in a session (or kind of, you will
indeed have multiple merkle tree for instance, one for each replica, but we can
easily prefix the column with the replica name if need be).
> 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
