https://issues.apache.org/jira/browse/SOLR-1170
-Bryan
On May 15, 2009, at May 15, 12:24 AM, Noble Paul നോബിള്
नोब्ळ् wrote:
the replication relies on lucene API to know what are the files
associated with an index version. If it returns the lock file also it
is replicated too.
I guess we must ignore the .lock file if it is returned in the list
of files.
you can raise an issue and we can fix it.
--Noble
On Fri, May 15, 2009 at 12:38 AM, Bryan Talbot
<btal...@aeriagames.com> wrote:
When using solr 1.4 replication, I see that the lucene-write.lock
file is
being replicated to slaves. I'm importing data from a db every 5
minutes
using cron to trigger a DIH delta-import. Replication polls every 60
seconds and the master is configured to take a snapshot
(replicateAfter)
commit.
Why should the lock file be replicated to slaves?
The lock file isn't stale on the master and is absent unless the
delta-import is in process. I've not tried it yet, but with the
lock file
replicated, it seems like promotion of a slave to a master in a
failure
recovery scenario requires the manual removal of the lock file.
-Bryan
--
-----------------------------------------------------
Noble Paul | Principal Engineer| AOL | http://aol.com
