[
https://issues.apache.org/jira/browse/SOLR-8227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15048131#comment-15048131
]
Ishan Chattopadhyaya edited comment on SOLR-8227 at 12/9/15 6:28 AM:
---------------------------------------------------------------------
bq. if a non-leader doesn't have a particular update
I meant "if a non-leader doesn't have a particular update in *its tlog*". An
update here could be an Add or a Delete. The effect of an update will always be
in the index in the form of a document (or absence of it), but peer sync works
when updates are streamed from leader to recovering replica.
was (Author: ichattopadhyaya):
bq. if a non-leader doesn't have a particular update
I meant "if a non-leader doesn't have a particular update in its tlog". An
update here could be an Add or a Delete. The effect of an update will always be
in the index in the form of a document (or absence of it), but peer sync works
when updates are streamed from leader to recovering replica.
> 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: [email protected]
For additional commands, e-mail: [email protected]
