cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stu Hood (JIRA)" <j...@apache.org>
Subject [jira] Updated: (CASSANDRA-193) Proactive repair
Date Fri, 31 Jul 2009 01:35:14 GMT

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

Stu Hood updated CASSANDRA-193:
-------------------------------

    Attachment: CASSANDRA-193.diff

Here is a first cut of the MerkleTree datastructure. There are a few issues that still need
work:

 * TreeRange.validate(Iterator) will need to take an iterator over ColumnFamily (Token,hash)
pairs. It currently takes an iterator over Tokens, and uses a dummy hash value,
 * We're still blocked by CASSANDRA-242: this patch contains a hacked implementation of Range.midpoint(Token,
Token) that only works with BigIntegerToken.

I'll start looking at CASSANDRA-242 for now so we can actually gets this integrated.

> Proactive repair
> ----------------
>
>                 Key: CASSANDRA-193
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-193
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Jonathan Ellis
>            Assignee: Stu Hood
>             Fix For: 0.5
>
>         Attachments: CASSANDRA-193.diff
>
>
> Currently cassandra supports "read repair," i.e., lazy repair when a read is done.  This
is better than nothing but is not sufficient for some cases (e.g. catastrophic node failure
where you need to rebuild all of a node's data on a new machine).
> Dynamo uses merkle trees here.  This is harder for Cassandra given the CF data model
but I suppose we could just hash the serialized CF value.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message