cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-6566) Differencer should not run in AntiEntropy Stage
Date Fri, 14 Feb 2014 21:46:19 GMT

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

Jonathan Ellis commented on CASSANDRA-6566:
-------------------------------------------

bq. I noticed it too and changed to send snapshot to the node itself. I think it is a mistake
to not include itself by looking at original CASSANDRA-3721.

If it's not a big change, I suggest pulling this out to a separate ticket for 1.2.

> Differencer should not run in AntiEntropy Stage
> -----------------------------------------------
>
>                 Key: CASSANDRA-6566
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6566
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: sankalp kohli
>            Assignee: Yuki Morishita
>            Priority: Minor
>             Fix For: 2.0.6
>
>         Attachments: 6566-2.0-v2.txt, 6566-2.0.txt
>
>
> The Differencing currently runs in AntiEntropy stage. When there are lot of ranges which
do not match, it takes sometime to compute the diff in ranges. Also with increase in Merkle
tree height it will take even more time in case of large diffs. 
> This causes other things to get blocked behind this. 
> Also no other repair messages can be processed.  
> Example: If a node is doing differencing for a repair, and Validation compaction is done
for another repair, it needs to block to send the tree over till Differencing is done.  



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message