lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Lu" <>
Subject Re: Memory eaten up by String, Term and TermInfo?
Date Sun, 14 Sep 2008 14:03:19 GMT
Can you try to update to the latest Lucene svn version, like yesterday?
LUCENE-1383 was checked in yesterday. This patch is addressing a leak
problem particular to J2EE applications.

Chris Lu
Instant Scalable Full-Text Search On Any Database/Application
Lucene Database Search in 3 minutes:
DBSight customer, a shopping comparison site, (anonymous per request) got
2.6 Million Euro funding!

On Sun, Sep 14, 2008 at 6:58 AM, Peter Cheng <>wrote:

> Hi the community,
> In a Tomcat application (a keyword-based search engine), I use Lucene 2.3.2
> to index 60 million documents, but each document is small-sized. The total
> index size is about 60GB.
> After a successful running for a week, Tomcat was down due to OutOfMemory.
> Then I restarted Tomcat, and after three days, I used jmap and jhat to find
> out what had eaten up the memory. I found millions of instances of String,
> Term, and TermInfo. Why?
> In my application, I use a single IndexSearcher object, which is shared by
> all the requests. It is opened initially, and will never be closed.
> What could have eaten up the memory? What is referring to millions of
> instances of Term and TermInfo?
> I can provide any snippets of codes if necessary.
> Thank you so much!
> Gong Cheng
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

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