lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Rodenburg" <>
Subject Re: Troubleshooting java heap out-of-memory
Date Tue, 03 Apr 2007 03:49:05 GMT
Thanks Yonik.  I'm not a java developer by trade, but the objects mentioned
in the heap dump along with the objects mentioned in the jira issue sound
eerily familiar to me.

Last year, we encountered a memory leak on the Lucene.Net project, stemming
from the FieldCache class having references left open after a Searcher had
been closed.  In troubleshooting that memory leak, we compared the
Lucene.Net code to the Java version, wondering why there might be a
difference.  In C#, there's no such thing as a WeakHashMap (what was used in
Java lucene at the time, if my memory serves correctly.)  We resolved our
issue by forcing a close of the FieldCache objects whenever its referencing
Searcher was closed.  In process of troubleshooting that issue, the memory
dump of the C# heap showed a lot of the same types of objects, and the
scenario was the same as what we've been experiencing (searchers closing and
refreshing for new changes).

We're going to investigate repetition of the error in our current test
environment, then run the latest solr bits (with the patched lucene version)
with the same scenario and see if the condition improves.

Thanks to all for your support on this issue.


On 4/2/07, Yonik Seeley <> wrote:
> On 4/2/07, Jeff Rodenburg <> wrote:
> > Yonik - is this the JIRA entry you're referring to?
> >
> >
> Yes.  But from the heap dump you provided, that doesn't look like the
> issue.
> -Yonik

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message