cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "sankalp kohli (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-6566) Differencer should not run in AntiEntropy Stage
Date Mon, 17 Feb 2014 18:04:19 GMT


sankalp kohli commented on CASSANDRA-6566:

"Since differencers are now tracked as a Set with this change, why don't we make the set concurrent
and remove the synchronize from the method."
- I am fine dropping this change since it is hardly a problem. 

v3 looks good. 

> Differencer should not run in AntiEntropy Stage
> -----------------------------------------------
>                 Key: CASSANDRA-6566
>                 URL:
>             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
> 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

View raw message