[ https://issues.apache.org/jira/browse/SOLR-8227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14994776#comment-14994776 ]
Varun Thacker commented on SOLR-8227: ------------------------------------- That should not be a problem no? At point X when the replica starts recovering from a leader the leader has the latest data . The replica also starts accepting documents while it it recovering so even if the leader changes at this point it would still have the latest data. > Recovering replicas should be able to recover from any active replica > --------------------------------------------------------------------- > > Key: SOLR-8227 > URL: https://issues.apache.org/jira/browse/SOLR-8227 > Project: Solr > Issue Type: Improvement > Reporter: Varun Thacker > > Currently when a replica goes into recovery it uses the leader to recover. It > first tries to do a PeerSync. If thats not successful it does a > replication. Most of the times it ends up doing a full replication because > segment merging, autoCommits causing segments to be formed differently on the > replicas ( We should explore improving that in another issue ) . > But when many replicas are recovering and hitting the leader, the leader can > become a bottleneck. Since Solr is a CP system , we should be able to recover > from any of the 'active' replicas instead of just the leader. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org