cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-193) Proactive repair
Date Sun, 06 Dec 2009 12:36:18 GMT

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

Hudson commented on CASSANDRA-193:
----------------------------------

Integrated in Cassandra #279 (See [http://hudson.zones.apache.org/hudson/job/Cassandra/279/])
    add manual repair through NodeProbe; patched by Stu Hood, reviewed by junrao for 
add AntiEntropyService; patched by Stu Hood, reviewed by junrao for 
preparation for AntiEntropyService; patched by Stu Hood, reviewed by junrao for 
add Merkle tree; patched by Stu Hood, reviewed by junrao for 
preparation for Merkle tree; patched by Stu Hood, reviewed by junrao for 


> 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: 193-1-tree-preparation.diff, 193-1-tree-preparation.diff, 193-1-tree-preparation.diff,
193-1-tree-preparation.diff, 193-2-tree.diff, 193-2-tree.diff, 193-2-tree.diff, 193-2-tree.diff,
193-3-aes-preparation.diff, 193-3-aes-preparation.diff, 193-3-aes-preparation.diff, 193-3-aes-preparation.diff,
193-4-aes.diff, 193-4-aes.diff, 193-4-aes.diff, 193-4-aes.diff, 193-5-manual-repair.diff,
193-5-manual-repair.diff, 193-5-manual-repair.diff, 193-6-inverted-filter.diff, 193-6-inverted-filter.diff,
193-6-repair-explanation-and-node-rename.diff, 193-7-disable-caching-and-fix-minimum-token.diff,
193-breakdown.txt, 193-breakdown.txt, mktree-and-binary-tree.png
>
>
> 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