Thanks Erick. Indexing is not happening to the slave since it has never been set up there - there aren't even any commits happening on the slave (which we normally do via cron job). But Indexing is definitely happening to the master at the time replication happens.
" Sounds like the master is still indexing and you've deleted documents on the master.": Yes, that's exactly what I suspect is happening. But if that's true, I'd like to understand how those deletes could find there way into being replicated to the slave when the only commit happening on the master was presumably completed before the replication. Do deletes get committed in some special way outside of an explicit commit? Or do they get copied over to the slave as part of the replication and therefore effectively get committed to the slave before they are committed to the master? My replication is configured to replicate after commit and after startup. The slave polls the master every 10 minutes. The master commits only once a day. Presumably the only time the number of documents changes is at the end of the commit. Then once the commit is done I'd expect replication to begin. So in order to end up with a different numDocs in the slave there would need to be some sort of commit happening during the replication, right? Frank -----Original Message----- From: Erick Erickson [mailto:erickerick...@gmail.com] Sent: Friday, February 28, 2014 9:22 PM To: solr-user@lucene.apache.org Subject: Re: Solr 4.5.0 replication numDocs larger in slave 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 > > >
