RE: index demo throws LockObtainFailedException

2010-01-29 Thread Teruhiko Kurosaka
Thank you, Otis and Mike! I verified that the older verison of Lucene (2.3.1) works w/o a problem like this on this machine. Kuro - To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail:

Re: index demo throws LockObtainFailedException

2010-01-29 Thread Michael McCandless
Likely you'll have to modify the demo to use SimpleFSLockFactory -- NativeFSLockFactory (now the default for Lucene, as of 2.9) often does not work on NFS. Mike On Thu, Jan 28, 2010 at 8:15 PM, Teruhiko Kurosaka wrote: > We have many Linux machines of different brands, sharing the same NFS > fi

Re: index demo throws LockObtainFailedException

2010-01-28 Thread Otis Gospodnetic
Otis Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch Hadoop ecosystem search :: http://search-hadoop.com/ - Original Message > From: Teruhiko Kurosaka > To: "java-user@lucene.apache.org" > Sent: Thu, January 28, 2010 8:15:26 PM > Subject: index demo throw

index demo throws LockObtainFailedException

2010-01-28 Thread Teruhiko Kurosaka
We have many Linux machines of different brands, sharing the same NFS filesystem for home. The Lucene file indexing demo program is failing with LockObainFailedException only on one particular Linux machine (Fedora Core 4, x86). I am including the console output at the bottom of this message.

Re: LockObtainFailedException

2009-11-02 Thread Michael McCandless
t; > Thanks > > - Chris > > - Original Message - > From: Anshum > Sent: Mon, 11/2/2009 10:08am > To: java-user@lucene.apache.org > Subject: Re: LockObtainFailedException > > Hi Chris, > > Isn't there a reply @ the older thread? > In case there is

Re: LockObtainFailedException

2009-11-02 Thread Anshum
-- > From: Anshum > Sent: Mon, 11/2/2009 10:08am > To: java-user@lucene.apache.org > Subject: Re: LockObtainFailedException > > Hi Chris, > > Isn't there a reply @ the older thread? > In case there isn't, this is generally observed when an indexwriter is not >

RE: LockObtainFailedException

2009-11-02 Thread Chris Bamford
apache.org Subject: Re: LockObtainFailedException Hi Chris, Isn't there a reply @ the older thread? In case there isn't, this is generally observed when an indexwriter is not closed properly i.e. just not closed. The lock is created on opening the indexwriter to maintain the sanity of

Re: LockObtainFailedException

2009-11-02 Thread Anshum
iter.close(). In case of exceptions, when the indexwriter.close() is not closed, the subsequent call to an index operation (opening a writer) would result in a lockobtainfailedexception. Try using a finally block to handle such cases. -- Anshum Gupta Naukri Labs! http://ai-cafe.blogspot.com The facts

LockObtainFailedException

2009-11-02 Thread Chris Bamford
Hi, I was researching LockObtainFailedExceptions and came across this thread. I don't use Solr, just regular Lucene deployed via Tomcat - but I have started getting these exceptions which coincides with our recent upgrade from 2.0.0 to 2.4.0. I have found that just removing the lock file seems to