No, I am using FSDirectory. Unfortunately, my indexes are over 2 GB in size
and I don't have a server that has that much free memory just for the
indexes.
If you figure out anything, let me know just in case it helps my case as
well. Thanks.
chrislusf wrote:
>
> Are you using RAMDirectory?
>
If I don't keep the IndexSearcher as a Singleton and instead open and close a
new one each time, I have a large memory leak (probably due to the large
queries I am doing). After watching the memory a while, I still believe I
have a small memory leak even when the Directory, Analyzer, and
IndexSear
I took your advice and created Singletons for the Directory, Analyzer, and
IndexSearcher classes. I also undid the closing of the Directory and
IndexSearcher. This seemed to fix my memory leak problem. However, I don't
like the fact that I am leaving open the IndexSearcher for the entire life
of a
As stated in my original message, I am closing the IndexSearcher elsewhere. I
don't close it in the method I copied because otherwise I lose access to the
Hits that come back.
You should really close the IndexSearcher rather than the directory.
Andy33 wrote:
> I have a memory le
--
View this message in context:
http://www.nabble.com/Lucene-Memory-Leak-tp19276999p19277001.html
Sent from the Lucene - Java Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addition
I have a memory leak in my lucene search code. I am able to run a few queries
fine, but I eventually run out of memory. Please note that I do close and
set to null the ivIndexSearcher object elsewhere. Here is the code I am
using...
private synchronized Hits doQuery(String field, String querySt
