Thanks Greg. We optimize the master once a week (early in the day Sunday) and we do not do a commit Sunday evening (the only evening of the week when we do not commit). So now after optimization/replication the master/slave pair that were out on sync on Friday now have the same numDocs (and every other value on the Overview page agrees except "size" under Replication where it shows the slave is smaller). Unfortunately, a different master/slave pair now have different numDocs after the optimize and replication done yesterday.
For the newly out of sync master/slave pair, the Version (Under Statistics on the Overview page) is 4 revisions earlier on the slave than on the master and there are two fewer segments on the slave than there are on the master. Under Replication on the Overview page, the Versions and Gen's are all the same, but the size of the slave is smaller than the master. The slave has 51 fewer documents than the master. But indexing is continuing on the master (but no commit has happened since the optimization early Sunday.) I wonder if this is related to the NRT functionality in some way. I see "Impl: org.apache.solr.core.NRTCachingDirectoryFactory" on the Overview page. I've been trying to rely on default behavior whenever possible. But perhaps I need to turn something off? Frank -----Original Message----- From: Greg Walters [mailto:greg.walt...@answers.com] Sent: Monday, March 03, 2014 10:00 AM To: solr-user@lucene.apache.org Subject: Re: Solr 4.5.0 replication numDocs larger in slave 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 >> >> >>
