You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Yuki Morishita (JIRA)" <ji...@apache.org> on 2014/02/14 03:35:20 UTC

[jira] [Updated] (CASSANDRA-6566) Differencer should not run in AntiEntropy Stage

     [ https://issues.apache.org/jira/browse/CASSANDRA-6566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yuki Morishita updated CASSANDRA-6566:
--------------------------------------

    Attachment: 6566-2.0.txt

(also: https://github.com/yukim/cassandra/tree/6566-1)

Two improvements in the patch:

* Remove snapshot latch so that snapshotting does not block ANTI_ENTROPY stage.
* Move differencers from ANTI_ENTROPY stage to different executor.



> 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
>            Priority: Minor
>         Attachments: 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)