Cao Manh Dat created SOLR-12504:
-----------------------------------
Summary: Leader should compute its fingerprint and retrieve recent
updates in an atomic way
Key: SOLR-12504
URL: https://issues.apache.org/jira/browse/SOLR-12504
Project: Solr
Issue Type: Bug
Security Level: Public (Default Security Level. Issues are Public)
Reporter: Cao Manh Dat
Assignee: Cao Manh Dat
SOLR-11216 solved many cases in the PeerSync (in doing recovery). But there are
still cases when PeerSync will be failed because of mismatch in fingerprint
comparison. The main reason here is fingerprint and recent versions of leader
is not computed/retrieved in an atomic way.
For example: when an update made into leader's tlog after fingerprint is
computed but before recent versions are retrieved.
Leader's fingerprint : (contains updates from 1-10)
Leader's recent versions : (contains updates from 1-12)
Replica's fingerprint : (contains updates from 1-12)
But it seems that blocking updates in leader for {{getVersions}} operation is
not a good idea. Still struggling on finding a solution.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
