[
https://issues.apache.org/jira/browse/SOLR-12969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16679971#comment-16679971
]
Cao Manh Dat commented on SOLR-12969:
-------------------------------------
I confirm that this problem happens on different versions of Solr (maybe from
the start since this is problem of PeerSync logic).
Attached patch here that fix the problem, but I really don't like the way we
current do PeerSync. I may think about this for couple of days before
committing the patch.
P/S: The scenario when this failure happen is tricky and this bug appear with
the appearance of SolrCloud so we don't have to rush about it.
> Solr replication failure
> ------------------------
>
> Key: SOLR-12969
> URL: https://issues.apache.org/jira/browse/SOLR-12969
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: replication (java)
> Reporter: Jeremy Smith
> Assignee: Cao Manh Dat
> Priority: Major
> Attachments: SOLR-12969.patch
>
>
> Under certain circumstances, replication fails between a leader and follower.
> The follower will not receive updates from the leader, even though the
> leader has a newer version. If the leader is restarted, it will get the
> older version from the follower.
>
> This was discussed on the [mailing
> list|https://mail-archives.apache.org/mod_mbox/lucene-solr-user/201810.mbox/%3CBYAPR04MB4406710795EA07E93BF80913ADCD0%40BYAPR04MB4406.namprd04.prod.outlook.com%3E]
> and [~risdenk] [wrote a
> script|https://github.com/risdenk/test-solr-start-stop-replica-consistency]
> that demonstrates this error. He also verified that the error occurs when
> the script is run outside of docker.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
