Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Fri, 28 Feb 2014 05:00:20 +0000 (UTC)
From: "sankalp kohli (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12688173.1389317127779.122772.1393563620970@arcas>
In-Reply-To: <JIRA.12688173.1389317127779@arcas>
References: <JIRA.12688173.1389317127779@arcas>
Subject: [jira] [Commented] (CASSANDRA-6566) Differencer should not run in
 AntiEntropy Stage
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

sankalp kohli commented on CASSANDRA-6566:
------------------------------------------

Sure

> 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-v3.txt, 6566-2.0.txt, 6566-followup.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)