Re: IndexWriters and write locks

2010-11-11 Thread Michael McCandless
On Wed, Nov 10, 2010 at 2:40 PM, Uwe Schindler wrote: > Are you using NFS as filesystem? NFS is incompatible to lucene :-) Actually Lucene can work over NFS, except, it's not a well tested combination. However, because NFS does not protect open files from deletion, you must use an app-specific d

Re: IndexWriters and write locks

2010-11-10 Thread Pulkit Singhal
> > > > -Original Message- > > From: Pulkit Singhal [mailto:pulkitsing...@gmail.com] > > Sent: Wednesday, November 10, 2010 2:55 PM > > To: java-user@lucene.apache.org > > Subject: Re: IndexWriters and write locks > > > > You know that really

RE: IndexWriters and write locks

2010-11-10 Thread Uwe Schindler
...@thetaphi.de > -Original Message- > From: Pulkit Singhal [mailto:pulkitsing...@gmail.com] > Sent: Wednesday, November 10, 2010 8:55 PM > To: java-user@lucene.apache.org > Subject: Re: IndexWriters and write locks > > You know that really confuses me. I've heard that st

RE: IndexWriters and write locks

2010-11-10 Thread Steven A Rowe
55 PM > To: java-user@lucene.apache.org > Subject: Re: IndexWriters and write locks > > You know that really confuses me. I've heard that stated a few times and > every time I just felt that it couldn't possibly be right. Maybe it was > meant in some very specific manner because o

Re: IndexWriters and write locks

2010-11-10 Thread Pulkit Singhal
lkit Singhal [mailto:pulkitsing...@gmail.com] > > Sent: Wednesday, November 10, 2010 7:57 PM > > To: java-user@lucene.apache.org > > Subject: Re: IndexWriters and write locks > > > > Thanks Uwe, that helps explain why the lock file is still there. > > > > The las

RE: IndexWriters and write locks

2010-11-10 Thread Uwe Schindler
0, 2010 7:57 PM > To: java-user@lucene.apache.org > Subject: Re: IndexWriters and write locks > > 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 &g

Re: IndexWriters and write locks

2010-11-10 Thread Pulkit Singhal
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: java.nio.channels.OverlappingFileLockException at sun.nio.ch.FileChannelImpl$SharedFileLockTable.checkList(FileChannelImpl.j

RE: IndexWriters and write locks

2010-11-10 Thread Uwe Schindler
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. - Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: u...@thetaphi.de > -O

Re: IndexWriters and write locks

2010-11-10 Thread Pulkit Singhal
I do not actually take the trouble to specify what Lock Factory to use, hmmm. Are you suggesting that because I'm using FSDirectory.open() in my code, I get a locking scheme that works ... while on other machine for other folks, they get one that runs into issues and throws java.nio.channels.Overl

Re: IndexWriters and write locks

2010-11-10 Thread Michael McCandless
Likely you are using NativeFSLockFactory? In which case, a leftover lock file does not mean the index is in fact locked, since the OS will [correctly] release the lock on process exit. Mike On Wed, Nov 10, 2010 at 9:38 AM, Pulkit Singhal wrote: > Hello, > > 1) On Windows, I often shut down my a