Your problem seems a lot like an issue I see with Near Real Time (NRT) replicas. I posted about it in this forum. I was told that a possible solution was to use the Global Stats feature. I am looking at testing that now.
Have you tried using Tlog replicas? That fixed my issues with relevancy differences between queries. On Mon, Feb 19, 2018 at 9:41 AM, Markus Jelsma <markus.jel...@openindex.io> wrote: > Hello, > > We're on 7.2.1 and rely on ExactStatsCache to work around the problem of > not all nodes sharing the same maxDoc within a shard. But, it doesn't work, > anymore! > > I've looked things up in Jira but nothing so far. SOLR-10952 also doesn't > cause it because with queryResultCache disabled, document scores don't > match up, the ordering of search results is not constant for the same query > in consecutive searches. > > We see this on a local machine, just with default similarity and classic > query parser. > > Any hints on what to do now? > > Many thanks, > Markus > -- This message and any attachment are confidential and may be privileged or otherwise protected from disclosure. If you are not the intended recipient, you must not copy this message or attachment or disclose the contents to any other person. If you have received this transmission in error, please notify the sender immediately and delete the message and any attachment from your system. Merck KGaA, Darmstadt, Germany and any of its subsidiaries do not accept liability for any omissions or errors in this message which may arise as a result of E-Mail-transmission or for damages resulting from any unauthorized changes of the content of this message and any attachment thereto. Merck KGaA, Darmstadt, Germany and any of its subsidiaries do not guarantee that this message is free of viruses and does not accept liability for any damages caused by any virus transmitted therewith. Click http://www.emdgroup.com/disclaimer to access the German, French, Spanish and Portuguese versions of this disclaimer.