I've tried different lucene locks to use, however I always get FNFE during
huge index update while IR reopens index. To prevent two IW at the same
time, I synchronize this operation using external locking mechanism based on
atomic filesystem operation like creating directory. So just before indexin
On Wed, Mar 9, 2011 at 2:44 PM, bart_212 wrote:
> Hi,
> I have two web applications that uses lucene 2.3.2. Both share the same
> index and can write or read. Writing is synchronized based on file system to
> allow only one IndexWriter to work at the moment. There can be multiple
> IndexReader. In
Usage sounds OK, but missing files on IndexReader.reopen definitely
doesn't sound OK.
2.3.2 is ancient and there have been many improvements since then.
I'd upgrade if possible.
You could also try losing the optimizes. On recent releases you don't
really need to use it. Not sure about 2.3.2 thou
