lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yonik Seeley (JIRA)" <>
Subject [jira] [Commented] (SOLR-8586) Implement hash over all documents to check for shard synchronization
Date Fri, 12 Aug 2016 17:15:22 GMT


Yonik Seeley commented on SOLR-8586:

You can set the environment variable solr.disableFingerprint to "false" to disable the fingerprint

If your indexes ever have updates to existing documents, then you're still risking OOMs anyway
(the first time a replica detects that an update may be reordered will cause the FieldCache
to be populated for _version_ for that segment).  The fingerprint makes that happen up-front
(what I meant to say in my previous message was "the maximum required amount of memory shouldn't
be changed").

> Implement hash over all documents to check for shard synchronization
> --------------------------------------------------------------------
>                 Key: SOLR-8586
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>          Components: SolrCloud
>            Reporter: Yonik Seeley
>            Assignee: Yonik Seeley
>             Fix For: 5.5, 6.0
>         Attachments: SOLR-8586.patch, SOLR-8586.patch, 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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message