On 9/12/2017 1:35 PM, ruby wrote: > No index change is happening in this case.
The duplicate document theory that Jason mentioned is one possibility. If you have a uniqueKey defined in your schema, then duplicates would need to have different uniqueKey values. If you index a document where the uniqueKey field has the same as an existing document, the existing document is deleted. If the index is not changing, and you don't have duplicate documents, then the only way I can imagine that happening is if there are multiple replicas of your collection with different numbers of deleted documents. Deleted documents are still part of the index, so their contents can affect the scores in your query results. When different replicas have different numbers of deleted documents, running the same query more than once when there is load balancing can have different score-based ordering on each of those queries. Multiple replicas with different numbers of deletes is common with SolrCloud, but it is also possible to have it with a non-SolrCloud install, though it probably is less likely. Thanks, Shawn
