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] [Commented] (CASSANDRA-5839) Save repair data to system table
Date Fri, 02 Aug 2013 04:05:48 GMT

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

Jonathan Ellis commented on CASSANDRA-5839:
-------------------------------------------

Something like this:

{code}
CREATE TABLE repair_sessions (
  keyspace text,
  columnfamily text,
  id timeuuid,
  range_begin text,
  range_end text,
  started_at timestamp,
  finished_at timestamp,
  PRIMARY KEY ((keyspace, columnfamily), id)
);
{code}

One interesting question is, do we make this per-machine or normally replicated?  The latter
makes querying it much simpler since you don't have to aggregate and de-duplicate across the
cluster.
                
> Save repair data to system table
> --------------------------------
>
>                 Key: CASSANDRA-5839
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5839
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core, Tools
>            Reporter: Jonathan Ellis
>            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: http://www.atlassian.com/software/jira

Mime
View raw message