Hey,
Currently we are using solr 4.0 with a master slave setup. The data gets
indexed on the master and then we issue a fetchindex command to replicate
it on the slave. The slave has a postCommit listener which gets kicked off
when replication finishes and we depend on this listener to know whn
replication is done. But when I tried to do the same with 4.2, the commit
does not seem to be happening. Is this a known issue? is there any other
way to know that replication is done?
Also, initially when i tried solr 4.2, i noticed with this setup, i noticed
that with the fetchIndex command, the fields were downloaded to the temp
folder, but it was never pulled into the index directory on the slave. The
only file which made it was the lock file. This problem does not happen
anymore?
Thanks,
Rohit

Reply via email to