I just ran into an issue similar to this that effected document scores on distributed searches. You might try doing an optimize and purging your deleted documents while no indexing is being done then checking your counts. Once I optimized all my indexes the document counts on all of my cores matched up and scoring was consistent.
Thanks, Greg On Feb 28, 2014, at 8:22 PM, Erick Erickson <erickerick...@gmail.com> wrote: > That really shouldn't be happening IF indexing is shut off. Otherwise > the slave is taking a snapshot of the master index and synching. > > bq: The slave has about 33 more documents and one fewer > segements (according to Overview in solr admin > > Sounds like the master is still indexing and you've deleted documents > on the master. > > Best, > Erick > > > On Fri, Feb 28, 2014 at 11:08 AM, Geary, Frank > <frank.ge...@zoominfo.com>wrote: > >> Hi, >> >> I'm using Solr 4.5.0, I have a single master replicating to a single >> slave. Only the master is being indexed to - never the slave. The master >> is committed once each night. After the first commit and replication the >> numDoc counts are identical. After the next nightly commit and after the >> second replication a few minutes later, the numDocs has increased in both >> the master and the slave as expected, but numDocs is not the same in the >> master as it is in the slave. The slave has about 33 more documents and >> one fewer segements (according to Overview in solr admin). >> >> I suspect the numDocs may be in sync again after tonight, but can anyone >> explain what is going on here? Is it possible a few deletions got >> committed to the master but not replicated to the slave? >> >> Thanks >> >> Frank >> >> >>
