I have multiple JVMs on different machines accessing the shared file system. I don't really have multiple IndexWriters on the same JVM, I asked this just out of curiosity.
So I don't understand from your reply if it's safe to use NoLockFactory, or I should use SimpleFSLockFactory and unlock if needed? Shai On Wed, Dec 2, 2009 at 3:03 PM, Uwe Schindler <u...@thetaphi.de> wrote: > Hi Shai, > > > have other uses as well? What about multiple IndexWriters from the same > > JVM? > > This also needs a lock. But if it is guaranteed to only have one JVM > accessing the index, you can use an in-JVM-Locking mechanism which is > provided by > > http://lucene.apache.org/java/3_0_0/api/all/org/apache/lucene/store/SingleIn > stanceLockFactory.html<http://lucene.apache.org/java/3_0_0/api/all/org/apache/lucene/store/SingleIn%0AstanceLockFactory.html> > > > If NoLockFactory is not safe, then we can move to SimpleFSLockFactory, > and > > since we can guarantee by other means that only one IndexWriter attempts > > to > > write to the index, we can IndexWriter.unlock(Dir) if the lock exists. > > If you can guarantee that you only have *one* JVM and there may be multiple > IndexWriters, use above solution. > > Uwe > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-user-h...@lucene.apache.org > >