lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yonik Seeley (JIRA)" <>
Subject [jira] [Updated] (SOLR-7332) Seed version buckets with max version from index
Date Mon, 06 Apr 2015 21:00:13 GMT


Yonik Seeley updated SOLR-7332:
    Attachment: SOLR-7332.patch

Things good good in general.
I uploaded a version that should be faster with docvalues (although I haven't tested it for
performance).  Maintaining even a 1 element priority queue (as using search will do) will
be more expensive, esp since it will be natural to find a more competitive hit as we go through
the index.

I do wonder if in the future we can make the get-version-from-index asynchronous (i.e. put
it in another thread).  Seems like it should be fine as long as the VersionInfo write lock
is held (blocking updates).

> Seed version buckets with max version from index
> ------------------------------------------------
>                 Key: SOLR-7332
>                 URL:
>             Project: Solr
>          Issue Type: Sub-task
>          Components: SolrCloud
>            Reporter: Timothy Potter
>            Assignee: Timothy Potter
>         Attachments: SOLR-7332.patch, SOLR-7332.patch, SOLR-7332.patch, 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

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

View raw message