The short for is that different replicas in a shard have different commit point if you go by wall-clock time. So during heavy indexing, you can happen to catch the different counts. That really shouldn't happen, though, unless you're clearing the index first on the assumption that you're replacing the same docs each time....
One solution people use is to index to a "dark" collection, then use collection aliasing to atomically switch when the job is done. Best, Erick On Thu, May 3, 2018 at 11:55 AM, Satya Marivada <satya.chaita...@gmail.com> wrote: > Hi there, > > We have a solr (6.3.0) index which is being re-indexed every night, it > takes about 6-7 hours for the indexing to complete. During the time of > re-indexing, the index becomes flaky and would serve inconsistent count of > documents 70,000 at times and 80,000 at times. After the indexing is > completed, it serves the consistent and right number of documents that it > has indexed from the database. Any suggestions on this. > > Also solr writes to the same location as current index during re-indexing. > Could this be the cause of concern? > > Thanks, > Satya
