To add on that, keep in mind to disable queryResultCache or distributed stats 
won't work.

And to add on that, i do not think distributed stats will work for a single 
shard index anyway.

Regards,
Markus

 
 
-----Original message-----
> From:Erick Erickson <erickerick...@gmail.com>
> Sent: Thursday 7th June 2018 21:19
> To: solr-user <solr-user@lucene.apache.org>
> Subject: Re: Different solr score between stand alone vs cloud mode solr
> 
> Short form:
> 
> As docs are updated, they're marked as deleted until the segment is
> merged. This affects things like term frequency and doc frequency
> which in turn influences the score.
> 
> Due to how commits happen, i.e. autocommit will hit at slightly skewed
> wall-clock time, different segments are merged on different replicas
> of the same shard. Thus the scores can be slightly different
> 
> You can turn on distributed stats which will help with this:
> https://issues.apache.org/jira/browse/SOLR-1632
> 
> Best,
> Erick
> 
> On Thu, Jun 7, 2018 at 12:07 PM, Wei <weiwan...@gmail.com> wrote:
> > Hi,
> >
> > Recently we have an observation that really puzzled us.  We have two
> > instances of Solr,  one in stand alone mode and one is a single-shard solr
> > cloud with a couple of replicas.  Both are indexed with the same documents
> > and have same solr version 6.6.2.  When issue the same query, the solr
> > score from stand alone and cloud are different.  How could this happen?
> > With the same data, software version and query,  should solr score be
> > exactly same regardless of cloud mode or not?
> >
> > Thanks,
> > Wei
> 

Reply via email to