Hi,
Thanks for your reply.
I can't think of any way to ensure fair file descriptor usage when
there are many active instances of IndexSearcher (all containing
IndexReader) running. Our project installations tend to run on heavily
loaded sites, where a lot of information is read and written at the
Actually you do need to make a new IndexSearcher every time you
reopen a new IndexReader.
However, that should not lead to leaking file descriptors. All open
files are held by IndexReader (not IndexSearcher), so as long as you
are properly closing your IndexReader's you shouldn't use up
