Sure there is actually no optimizing on the slave needed,
but after calling optimize on the slave the write.lock will be removed.
So why is the replication process not doing this?
Regards
Bernd
Am 10.08.2011 10:57, schrieb Shalin Shekhar Mangar:
On Wed, Aug 10, 2011 at 1:11 PM, Bernd Fehling<
bernd.fehl...@uni-bielefeld.de> wrote:
From what I see on my slaves, yes.
After replication has finished and new index is in place and new reader has
started
I have always a write.lock file in my index directory on slaves, even
though the index
on master is optimized.
That is not true. Replication is roughly a copy of the diff between the
master and the slave's index. An optimized index is a merged and re-written
index so replication from an optimized master will give an optimized copy on
the slave.
The write lock is due to the fact that an IndexWriter is always open in Solr
even on the slaves.
