Anyone can tell me what was I doing wrong ? Is that the expected behavior (slave replicate entire index if on previous replication attempt the master was not available ) ?
On Thu, Apr 7, 2016 at 9:12 PM, Lior Sapir <lior.sa...@gmail.com> wrote: > Thanks for the reply. > > I easily re produced it in my "sandbox" env. Steps to re produce > 1. Setup a master > 2. Setup a slave in a different server > 3. The slave replicated the master index > 4. From now on not even a single document is added. No optimization or > what so ever is done on the master or slave > 5. I stop the master > 6. I start the master > 7. I see the slave is replicating/copying the entire index > > This is exactly what happened in production when I restarted the master. > > I attached the configurations files. > > Replication section: > > *Master:* > > <requestHandler name="/replication" class="solr.ReplicationHandler"> > <lst name="master"> > <str name="replicateAfter">commit</str> > </lst> > </requestHandler> > > *Slave:* > > <requestHandler name="/replication" class="solr.ReplicationHandler" > > <lst name="slave"> > <str name="masterUrl"> > http://solr01-isrl01.flr.local:8983/solr/replication-master/replication > </str> > <str name="pollInterval">00:00:60</str> > </lst> > </requestHandler> > > > > Best, > Lior > > On Thu, Apr 7, 2016 at 6:56 PM, Erick Erickson <erickerick...@gmail.com> > wrote: > >> What does your configuration file look like for the replication >> handler? Does this happen whenever you restart a slave even if >> _nothing_ has changed on the master? >> >> And this will certainly happen if you're optimizing the master before >> you restart, although that doesn't sound likely. >> >> Best, >> Erick >> >> On Thu, Apr 7, 2016 at 6:54 AM, Lior Sapir <lior.sa...@gmail.com> wrote: >> > Solr slave is doing full replication (entire index) of index after >> master >> > restart >> > Using solr 5.3.1 not cloud (using maser slave architecture ) I see that >> > slave replicates entire index after master restart even though the index >> > version is the same >> > >> > This is bad for me since the slave which is doing serving replicates >> 80gb >> > if I restart the server and our service is down >> > >> > I attached a file with some snippets of the slave log before and after >> the >> > master restart. >> > >> > Is there some default configuration issue causing this problem? >> > Both indexes master and slave were not updated for sure before and >> after the >> > master restart. >> > The index version stayed exactly the same. >> > >> > >> > >> > >
