[
https://issues.apache.org/jira/browse/SOLR-9446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15439918#comment-15439918
]
ASF GitHub Bot commented on SOLR-9446:
--------------------------------------
GitHub user praste opened a pull request:
https://github.com/apache/lucene-solr/pull/73
SOLR-9446 Do a fingerprint check before starting PeerSync
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/praste/lucene-solr SOLR-9446
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/lucene-solr/pull/73.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #73
----
commit 82e2fb5914a202f7577b92b999370cfb6fcc605b
Author: Pushkar Raste <[email protected]>
Date: 2016-08-26T17:50:40Z
SOLR-9446 Do a fingerprint check before starting PeerSync
----
> Just replicated index goes into replication recovery on leader failure even
> if index was not changed
> ----------------------------------------------------------------------------------------------------
>
> Key: SOLR-9446
> URL: https://issues.apache.org/jira/browse/SOLR-9446
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: replication (java)
> Reporter: Pushkar Raste
> Priority: Minor
>
> We noticed this issue while migrating solr index from machines {{A1, A2 and
> A3}} to {{B1, B2, B3}}. We followed following steps (and there were no
> updates during the migration process).
> * Index had replicas on machines {{A1, A2, A3}}. Let's say {{A1}} was the
> leader at the time
> * We added 3 more replicas {{B1, B2 and B3}}. These nodes synced with the by
> replication. These fresh nodes do not have tlogs.
> * We shut down one of the old nodes ({{A3}}).
> * We then shut down the leader ({{A1}})
> * New leader got elected (let's say {{A2}}) became the new leader
> * Leader asked all the replicas to sync with it
> * Fresh nodes (ones without tlogs), first tried PeerSync but since there was
> no frame of reference, PeerSync failed and fresh nodes fail back on to try
> replication
> Although replication would not copy all the segments again, it seems like we
> can short circuit sync to put nodes back in active state as soon as possible.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
