So if on startup index gets replicated, then commit probably isn't being called anywhere on master.
Is that index configured to autocommit on master, or do you commit from application code? If you commit from application code, check if commit actually gets issued to the slave. Regards, Stevo. On Thu, Jan 20, 2011 at 2:41 PM, Thomas Kellerer <spam_ea...@gmx.net> wrote: > Thomas Kellerer, 20.01.2011 12:53: >> >> Hi all, >> >> we have implemented a Solr based search in our web application. We >> have one master server that maintains the index which is replicated >> to the slaves using the built-in Solr replication. >> >> This has been working fine so far, but suddenly the replication does >> not send the modified files to the slaves. >> >> Each time the slave polls the master, the master answers with "No >> files to download for indexversion: 1291900430240" >> >> The problem is, that the index version on the master **is** higher >> than the one on the slave. >> > > One other thing I noticed: > > When I do > > http://host:port/solr/replication?command=indexversion > > on the slave, it returns 0 (zero) > > <response> > <lst name="responseHeader"> > <int name="status">0</int> > <int name="QTime">0</int> > </lst> > <long name="indexversion">0</long> > <long name="generation">0</long> > </response> > > But when I http://host:port/solr/core0/admin/replication/index.jsp on the > slave, it displays a "valid" indexversion. > > Don't know that that means though. > > Regards > Thomas > >
