Hi - see inline. Markus -----Original message----- > From:Shawn Heisey <apa...@elyograg.org> > Sent: Tuesday 8th March 2016 15:11 > To: solr-user@lucene.apache.org > Subject: Re: Different scores depending on cloud node > > On 3/8/2016 6:56 AM, Robert Brown wrote: > > I have 2 shards, each with 1 replica. > > > > When sending the same request to the cluster, I'm seeing the same > > results, but ordered differently, and with different scores. > > > > Does this highlight an issue with my index, or is this an accepted > > anomaly? > > SolrCloud's method of operation can result in a different number of > deleted documents on different replicas. Deleted documents that still > exist within the index can affect scores. Because SolrCloud picks an > available replica at random to satisfy queries, different requests will > use different replicas.
This is indeed a problem is your similarity relies on maxDoc. DocCount does not suffer from this problem. It becomes much more stable, although we still sometimes see tiny anomalies. > > Distributed IDF, available starting in version 5.0 and described on the > following documentation page, can help even these differences out, but > will not completely eliminate them: > > https://cwiki.apache.org/confluence/display/solr/Distributed+Requests > > The only way that I know of to completely wipe out these anomalies is to > optimize your collection. This will completely rewrite the index, > getting rid of deleted documents as it runs, which tends to be very slow > and can be very disruptive to Solr's performance. It will also block > deleteByQuery requests until it is finished. > > Thanks, > Shawn > >
