[
https://issues.apache.org/jira/browse/CASSANDRA-193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733076#action_12733076
]
Stu Hood commented on CASSANDRA-193:
------------------------------------
I'm making steady progress on this ticket. So far, the work has all been on
implementing the merkle tree data structure, but I'd like to start thinking
about integrating the structure soon.
I've been working in the (misnamed) branch 'binary-merkle' on
http://github.com/stuhood/cassandra-anti-entropy/. I may submit a patch here
containing just the data structure sometime soon, but it still has a wart that
I'm not happy about.
> 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
>
>
> 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.
