lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yonik Seeley (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-8586) Implement hash over all documents to check for shard synchronization
Date Mon, 01 Feb 2016 15:05:39 GMT

    [ https://issues.apache.org/jira/browse/SOLR-8586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15126352#comment-15126352
] 

Yonik Seeley commented on SOLR-8586:
------------------------------------

{quote}
PeerSync always returned "true" if the core doing the sync was judged to be either equal to
or ahead of the remote core.
So one outstanding question is: under what circumstances do we change this to only return
true on an exact match?
{quote}

So I think the answer to this is that we're OK, as long as *both* peers don't end up returning
true.

> 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
>          Components: SolrCloud
>            Reporter: Yonik Seeley
>         Attachments: SOLR-8586.patch, 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message