cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jimmy Mårdell (JIRA) <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-5839) Save repair data to system table
Date Thu, 12 Dec 2013 12:31:07 GMT

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

Jimmy Mårdell commented on CASSANDRA-5839:
------------------------------------------

I agree on changing the primary key, that's nice.

In an RDBMS I would agree on storing stats separately. Not as obvious in this case. What do
you consider stats (and not status) in the current schema?

There are other reasons for running repair than just ensuring tombstones are replicated, so
I don't think a hardcode factor based on gc_grace is the way to go.


> 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
>            Assignee: Jimmy Mårdell
>            Priority: Minor
>             Fix For: 2.0.4
>
>         Attachments: 2.0.4-5839-draft.patch
>
>
> As noted in CASSANDRA-2405, it would be useful to store repair results, particularly
with sub-range repair available (CASSANDRA-5280).



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)

Mime
View raw message