RE: Waiting for lock file problem

t: Re: Waiting for lock file problem OK, you're right (to expect/hope that Lucene's locking would work like this). Unfortunately all of Lucene's current LockFactory impls are overly simplistic: they try once per second (by default), up until your timeout, to acquire the lock. If they

Re: Waiting for lock file problem

nd then waiting 10 seconds to > throw and exception? > > Thanks again, > Billy > > ________________ > From: Michael McCandless [luc...@mikemccandless.com] > Sent: Friday, May 15, 2009 2:52 PM > To: java-user@lucene.apache.org > Subject: Re: Waiting for lock fil

RE: Waiting for lock file problem

ly checking once and then waiting 10 seconds to throw and exception? Thanks again, Billy From: Michael McCandless [luc...@mikemccandless.com] Sent: Friday, May 15, 2009 2:52 PM To: java-user@lucene.apache.org Subject: Re: Waiting for lock file problem You sho

Re: Waiting for lock file problem

You should try to share a single IndexWriter instance across "Build Indices" and "Application". Also, you shouldn't open a new IndexWriter for each document added (nor, call optimize), if possible. Lucene doesn't allow more than one IndexWriter to be open at once on the same index (the write lock

Waiting for lock file problem

I am trying to build my indices file while still allowing my application to add new information and I my application cannot obtain the lock. Here is a little pseudo code on what I am trying to do: Build Indicies: 1. For each element (i.e. I have n elements I want to add to the index) 2.