OK then index generation and index version are out of count when it comes to verify that master and slave index are in sync.
What else is possible? The strange thing is if master is 2 or more generations ahead of slave then it works! With your logic the slave must _always_ be one generation ahead of the master, because the slave replicates from master and then does an additional commit to recognize the changes on the slave. This implies that the slave acts as follows: - if the master is one generation ahaed then do an additional commit - if the master is 2 or more generations ahead then do _no_ commit OR - if the master is 2 or more generations ahead then do a commit but don't change generation and version of index Can this be true? I would say "not really". Regards Bernd Am 13.02.2013 20:38, schrieb Amit Nithian: > Okay so then that should explain the generation difference of 1 between the > master and slave > > > On Wed, Feb 13, 2013 at 10:26 AM, Mark Miller <markrmil...@gmail.com> wrote: > >> >> On Feb 13, 2013, at 1:17 PM, Amit Nithian <anith...@gmail.com> wrote: >> >>> doesn't it do a commit to force solr to recognize the changes? >> >> yes. >> >> - Mark >> >
