I found what the problem was: we were closing the IndexSearcher but not the
underlying IndexReader (I wrongly assumed that closing one would close the
other).
Everything is working perfectly now, thanks for the help.
JB
On 6 April 2011 22:13, Erick Erickson wrote:
> I suspect you're already awa
I suspect you're already aware of this, but I've
overlooked the obvious so many times I thought
I'd mention it...
A classic mistake is to assign a reader with reopen
and not close the old reader, see:
http://lucene.apache.org/java/3_0_1/api/core/org/apache/lucene/index/IndexReader.html#reopen()
<
Yes, to the best of my knowledge and experience, closing readers and
writers releases the file handles.
--
Ian.
On Wed, Apr 6, 2011 at 12:59 AM, Jean-Baptiste Reure
wrote:
> We are using version 3.0.3. So you can confirm that closing the writer (and
> the reader created from that writer) shoul
We are using version 3.0.3. So you can confirm that closing the writer (and
the reader created from that writer) should be enough to release the file
handles?
If that is the case, that means our application has a bug somewhere that i
need to track down.
Thanks,
JB.
On 5 April 2011 19:48, Ian Lea
Which version of lucene are you using? Something changed in the 3.x
release, and maybe 2.9.x, in the way that old file handles are closed.
Previously it wasn't always necessary to explicitly close everything,
now it is.
Your usage sounds fine to me. When I've hit too many open files when
using
Hi all,
I have been looking for information about this and found a few things here
and there but nothing very clear on when files are opened and closed by
Lucene.
We have an application that uses Lucene quite heavily in the following
fashion: there are multiple indexes in use at all times. For ea
