: Let me add some background. A user triggers an operation which under the
: hood needs to update a single field. Atomic update fails with a message
: that one of the mandatory fields is missing (which is strange by
: itself). When I query Solr for the exact document (fq with the document
: i
Mike Drob
Sent: יום ב 01 פברואר 2021 22:58
To: solr-user@lucene.apache.org
Subject: Re: Ghost Documents or Shards out of Sync
To expand on what Jason suggested, if the issue is the non-deterministic
ordering due to staggered commits per replica, you may have more consistency
with TLOG replicas rath
To expand on what Jason suggested, if the issue is the non-deterministic
ordering due to staggered commits per replica, you may have more
consistency with TLOG replicas rather than the NRT replicas. In this case,
the underlying segment files should be identical and lead to more
predictable results.
Forgot to answer your second question:
> Can I trigger the "fixing" mechanism that Solr runs at restart by an API call
> or some other method?
It depends on what the cause is. But for at least some possible
causes there is an API call that can resolve this. Though that API
itself (Solr's misna
Hi Ronen,
The first thing I'd figure out in your situation is whether the
results are actually different each time, or whether the ordering is
what differs (which might push a particular result off the page you're
looking at, giving the appearance that it didn't match).
In the case of the former,
Hi All,
I'm using Solr Cloud (version 8.3.0) with shards and replicas (replication
factor of 2).
Recently, I've encountered several times that running the same query
repeatedly yields different results. Restarting the nodes fixes the problem
(until next time).
I assume that some shards are not syn
