If you've got multiple IndexWriters on one index open at the same time then you must be messing with lucene's locking and all bets are off.
>From the javadocs for IndexWriter: Opening an IndexWriter creates a lock file for the directory in use. Trying to open another IndexWriter on the same directory will lead to a LockObtainFailedException. -- Ian. On Fri, Mar 4, 2011 at 8:56 PM, Brian Coverstone <br...@mainsequence.net> wrote: > I am a Lucene newbie, so I apologize beforehand if I am asking anything > silly, or that has been covered before. > > I am currently debugging a project using Lucene. The problem that is > happening is searches stop responding when an IndexWriter is writing to the > index. In going through the code, I am seeing where two or more IndexWriter > objects can be opened to the same index. However, only one IndexWriter is > used. Even though other IndexWriter objects are created but not used, would > their mere presence cause a problem? > > My other suspicion is the index has become corrupted because we have other > indexes that are working just fine. Though I've run a check and repair and > it seems to be clean. > > Any advice would be appreciated! > > Regards, > Brian Coverstone > --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail: java-user-h...@lucene.apache.org
