[
https://issues.apache.org/jira/browse/SOLR-9310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15381572#comment-15381572
]
Pushkar Raste commented on SOLR-9310:
-------------------------------------
On second thought, moving fingerprint check after log replay would not work as
it can contain updates other than the node received from the leader.
Only two options I could think of is
* Change the check in {{DistributedUpdateProcessor.versionAdd()}} to handle
{{PEER_SYNC}} flag (i.e. not to buffer updates from PEER_SYNC). I am not
entirely sure what other issues it might cause.
* Not to do the fingerprint check for after updates are applied in PeerSync if
core is not in active state.
> PeerSync fails on a node restart due to IndexFingerPrint mismatch
> -----------------------------------------------------------------
>
> Key: SOLR-9310
> URL: https://issues.apache.org/jira/browse/SOLR-9310
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Pushkar Raste
> Attachments: PeerSyncReplicationTest.patch
>
>
> I found that Peer Sync fails if a node restarts and documents were indexed
> while node was down. IndexFingerPrint check fails after recovering node
> applies updates.
> This happens only when node restarts and not if node just misses updates due
> reason other than it being down.
> Please check attached patch for the test.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
