cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Brown (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-5839) Save repair data to system table
Date Tue, 06 Aug 2013 13:41:48 GMT


Jason Brown commented on CASSANDRA-5839:

I think it should be replicated for ease of use, as I believe this feature is an ease of use
concern (for admins) so they don't have to rummage around in distributed log files.

Other items to capture might include the coordinator's hostname (I think we used to call that
node the 'initiator' back in the day) and the set of the endpoints participating in the repair
(possibly with datacenter).
> Save repair data to system table
> --------------------------------
>                 Key: CASSANDRA-5839
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core, Tools
>            Reporter: Jonathan Ellis
>            Assignee: Jason Brown
>            Priority: Minor
>             Fix For: 2.0.1
> As noted in CASSANDRA-2405, it would be useful to store repair results, particularly
with sub-range repair available (CASSANDRA-5280).

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:

View raw message