[
https://issues.apache.org/jira/browse/SOLR-8586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15418799#comment-15418799
]
Yonik Seeley edited comment on SOLR-8586 at 8/12/16 4:38 PM:
-------------------------------------------------------------
If the _version_ field doesn't have docValues, then it will be un-inverted
(i.e. FieldCache entries will be built to support _version_ lookups, and that
does require memory).
Since _version_ lookups are needed in the course of indexing anyway (to detect
update reorders on replicas), this should really just change when these
FieldCache entries are created... hence the maximum required amount of memory
shouldn't be changed.
was (Author: [email protected]):
If the _version_ field doesn't have docValues, then it will be un-inverted
(i.e. FieldCache entries will be built to support _version_ lookups, and that
does require memory).
Since _version_ lookups are needed in the course of indexing anyway (to detect
update reorders on replicas), this should really just change when these
FieldCache entries are created... hence the maximum required amount of memory
should be changed.
> 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
> 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
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
