Thanks Uwe, that helps explain why the lock file is still there.
The last piece of the puzzle is why someone may see exceptions such as the
following from time to time:
I suppose this means that the OS itself hasn't released the lock even after
I shut down my application server and restarted it.
Am I right?
Or is there something else that can possibly be the culprit (in anyone's
experience) that I can investigate?
On Wed, Nov 10, 2010 at 12:57 PM, Uwe Schindler wrote:
This is because Lucene uses Native Filesystem Locks. The lock file itself
is just a placeholder which is not cleaned up on Ctrl-C. The lock is not the
file itself, its *on* the file.
H.-H.-Meier-Allee 63, D-28213 Bremenhttp://www.thetaphi.de
From: Pulkit Singhal
Sent: Wednesday, November 10, 2010 3:38 PM
Subject: IndexWriters and write locks
1) On Windows, I often shut down my application server (which has active
IndexWriters open) using the ctrl+c keys.
2) I inspect my directories on the file system I see that the write.lock
file is still
3) I start the app server again, and do some operations that would require
IndexWriters to write to the same directories again and it works!
I don't understand why I do not run into any exceptions?
I mean there is already a lock file present which should prevent the
IndexWriters from getting access to the directories ... no?
I should be happy but I'm not because other folks are able to get
when they bounce their servers an I'm unable to reproduce the problem and I
can't help them.
Any clues? Anyone?
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org