[
https://issues.apache.org/jira/browse/SOLR-7332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14391729#comment-14391729
]
Timothy Potter commented on SOLR-7332:
--------------------------------------
[[email protected]] for the first issue, I'm curious if you think trying to
initialize the buckets during core initialization (after there is a searcher
but before updates are accepted) is the way to go? That was my first thought,
but maybe it would be better to invoke the initialization from the
{{DistributedUpdateProcessor#versionAdd}} method, which is where it is needed.
The incoming update will block until the query returns, but that should only be
once. Of course that would add a synchronization point for every doc, which
isn't ideal either.
> Seed version buckets with max version from index
> ------------------------------------------------
>
> Key: SOLR-7332
> URL: https://issues.apache.org/jira/browse/SOLR-7332
> Project: Solr
> Issue Type: Sub-task
> Components: SolrCloud
> Reporter: Timothy Potter
> Assignee: Timothy Potter
> Attachments: SOLR-7332.patch
>
>
> See full discussion with Yonik and I in SOLR-6816.
> The TL;DR of that discussion is that we should initialize highest for each
> version bucket to the MAX value of the {{__version__}} field in the index as
> early as possible, such as after the first soft- or hard- commit. This will
> ensure that bulk adds where the docs don't exist avoid an unnecessary lookup
> for a non-existent document in the index.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
