[
https://issues.apache.org/jira/browse/SOLR-8586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15118332#comment-15118332
]
Yonik Seeley commented on SOLR-8586:
------------------------------------
bq. Could you please clarify what this issue is all about? I don't get it.
Are you familiar with PeerSync? I just linked SOLR-8129 as well.
PeerSync currently checks for replicas being in-sync by looking at the last 100
updates, and if there are only a few updates missing (judged by a sufficient
overlap of those updates) it will grab the missing updates from the peer and
then assume that it is in sync. For whatever reason, updates can sometimes get
wildly reordered, and looking at the last N updates is not sufficient.
Hopefully "Implement hash over all documents to check for shard
synchronization" should now make sense?
> Implement hash over all documents to check for shard synchronization
> --------------------------------------------------------------------
>
> Key: SOLR-8586
> URL: https://issues.apache.org/jira/browse/SOLR-8586
> Project: Solr
> Issue Type: Improvement
> Reporter: Yonik Seeley
> Attachments: SOLR-8586.patch
>
>
> An order-independent hash across all of the versions in the index should
> suffice. The hash itself is pretty easy, but we need to figure out
> when/where to do this check (for example, I think PeerSync is currently used
> in multiple contexts and this check would perhaps not be appropriate for all
> PeerSync calls?)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
