lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (SOLR-7625) Version bucket seed not updated after new index is installed on a replica
Date Tue, 02 Jun 2015 20:15:49 GMT


ASF subversion and git services commented on SOLR-7625:

Commit 1683174 from [~thelabdude] in branch 'dev/trunk'
[ ]

SOLR-7625: Ensure that the max value for seeding version buckets is updated after recovery
even if the UpdateLog is not replayed.

> Version bucket seed not updated after new index is installed on a replica
> -------------------------------------------------------------------------
>                 Key: SOLR-7625
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>          Components: SolrCloud
>    Affects Versions: 5.2
>            Reporter: Timothy Potter
>            Assignee: Timothy Potter
>            Priority: Blocker
>             Fix For: 5.2
>         Attachments: SOLR-7625.patch
> This is related to SOLR-7332 ... I used to set the highest value on the version buckets
based on a lookup to the index whenever a firstSearcher event fired, but that led to reentrant
lock issues (see SOLR-7587), so I moved that version seeding code into the SolrCore constructor.
> While working on SOLR-4506, I just realized that if a core has to pull index files from
the leader to recover, then the version bucket doesn't get updated once the new index files
are pulled over. In other words, the code seeds the version buckets during core init, but
if the underlying index changes due to being too far out-of-date, then the version buckets
are never updated once the new index is in place. The risk is that if bucket versions are
seeded with a value that is too low, then it can lead to correctness issues with versioned

This message was sent by Atlassian JIRA

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

View raw message