You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Brandon Williams (JIRA)" <ji...@apache.org> on 2010/11/10 00:14:24 UTC

[jira] Commented: (CASSANDRA-1719) improve read repair

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

Brandon Williams commented on CASSANDRA-1719:
---------------------------------------------

I get odd behavior testing this patch.  Three node cluster, rf=2.  I start them up, take one down after the others see it, then insert data.  If I read it back with the node down, that works, but when I bring it up all kinds of keys are missing (even though I don't read from it directly.)  If I take it back down, everything works again.

> improve read repair
> -------------------
>
>                 Key: CASSANDRA-1719
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1719
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Jonathan Ellis
>            Assignee: Jonathan Ellis
>            Priority: Minor
>             Fix For: 0.6.8, 0.7.0
>
>         Attachments: 1719.txt
>
>
> Read repair recomputes the local digest for each replica, which is a lot of wasted CPU on large reads

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