[ https://issues.apache.org/jira/browse/CASSANDRA-6566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13902148#comment-13902148 ]
sankalp kohli commented on CASSANDRA-6566: ------------------------------------------ Comments on v2 patch Since terminate method on RepairJob is empty, why not remove it. Also remove from where it is called in RepairSession. Though not a part of this patch, but terminate method in RepairSession sounds like you are terminating something. When it fact it cleans stuff up after finishing. > 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)