Re: Query results change

2016-01-26 Thread Toke Eskildsen
On Mon, 2016-01-25 at 20:38 -0700, Shawn Heisey wrote: > Very likely what's happening is that sometimes your shards are > responding on a different timescale with each request, so the pieces > that get combined into the final result set arrive in a different > order. This causes the Java object co

Re: Query results change

2016-01-25 Thread Shawn Heisey
On 1/25/2016 7:47 PM, Brian Narsi wrote: > We have increased the number of documents in the SolrCloud collection to > several million now and are seeing the "issue" again: > > If there are 10 documents each with exactly the same highest score and we > run the query again and again, the order of doc

Re: Query results change

2016-01-25 Thread Brian Narsi
We have increased the number of documents in the SolrCloud collection to several million now and are seeing the "issue" again: If there are 10 documents each with exactly the same highest score and we run the query again and again, the order of documents changes. So strictly speaking although all

Re: Query results change

2016-01-15 Thread Brian Narsi
Data is indexed using Data Import Handler with clean=true, commit=true and optimize=true. After that there are no updates or delete. The setup is SolrCloud with 2 shards and 2 replicas each. If the data and query has not changed, one expects to see the same results on repeated searches; so it is

Re: Query results change

2016-01-15 Thread Erick Erickson
Probably the fact that information from deleted/updated documents is still hanging around in the corpus until merged away. The nub of the issue is that terms in deleted documents (or the replaced doc if you update) still influence tf/idf calculations. If you optimize as Binoy suggests, all of the

Re: Query results change

2016-01-15 Thread Binoy Dalal
You should try debugging such queries to see how exactly they're being executed. That will give you an idea as to why you're seeing the results you see. On Fri, 15 Jan 2016, 19:05 Brian Narsi wrote: > We have an index of 25 fields. Currently number of records in index is > about 120,000. We are

Query results change

2016-01-15 Thread Brian Narsi
We have an index of 25 fields. Currently number of records in index is about 120,000. We are using parser: edismax qf: contains 8 fields fq: 1 field mm = 1 qs = 6 pf: containing g 3 fields bf: containing 1 field We have noticed that sometimes results change between two searches even if ever