I have confirmed that the OutOfMemoryError is not Lucene's problem. It's
just because JVM failed to perform GC when necessary, and I don't know why.
To fix this, I started another thread to call GC every six hours, and
problems got solved.
Thank you all.
Gong
> -----Original Message-----
> From: Michael McCandless [mailto:lucene@mikemccandless.com]
> Sent: Sunday, September 14, 2008 10:28 PM
> To: java-user@lucene.apache.org
> Subject: Re: Memory eaten up by String, Term and TermInfo?
>
>
> Small correction: it was checked in this morning (at least, on the
> East Coast of the US).
>
> So you need to either build your own JAR using Lucene's trunk, or,
> wait for tonite's build to run and then download the build artifacts
> from here:
>
> http://hudson.zones.apache.org/hudson/job/Lucene-trunk
>
> If possible, please report back if this fixed your OutOfMemoryError.
>
> 2.4 will include this fix.
>
> Mike
>
> Chris Lu wrote:
>
> > 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
> > site: http://www.dbsight.net
> > demo: http://search.dbsight.com
> > Lucene Database Search in 3 minutes:
> >
> http://wiki.dbsight.com/index.php?title=Create_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
> > <petercheng456@gmail.com>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: java-user-unsubscribe@lucene.apache.org
> >> For additional commands, e-mail: java-user-help@lucene.apache.org
> >>
> >>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-user-help@lucene.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org
|