The autocommit settings on leaders and replicas can be slightly offset in terms of wall clock time so docs that have been committed on one node may not have been committed on the other. Your comment that you can optimize and fix this is evidence that this is what you're seeing.
to test this: 1> stop indexing 2> issue a "commit" to the collection. If that shows all replicas with the same count, then the above is the explanation. Best, Erick On Mon, Nov 21, 2016 at 6:52 PM, Lewin Joy (TMS) <lewin....@toyota.com> wrote: > ** PROTECTED 関係者外秘 > Hi, > > I am having a strange issue working with solr 6.1 cloud setup on zookeeper > 3.4.8 > > Intermittently after I run Indexing, the replicas are having a different > record count. > And even though there is this mismatch, it is still marked healthy and is > being used for queries. > So, now I get inconsistent results based on the replica used for the query. > > This gets resolved after restarting solr servers. Or if I just do an optimize > on the collection. > > Any idea what could be wrong? Have any of you faced something similar? > Is there some configuration or setting I should be checking? > > > Thanks, > Lewin
