lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yonik Seeley" <>
Subject Re: Troubleshooting java heap out-of-memory
Date Mon, 02 Apr 2007 20:10:39 GMT
On 4/1/07, Jeff Rodenburg <> wrote:
> Our scenario: 150MB index, 140000 documents, read/write servers in place
> using standard replication.  Running Tomcat 5.5.17 on Redhat Enterprise
> Linux 4.  Java configured to start with -Xmx1024m.  We encounter java heap
> out-of-memory issues on the read server at staggered times, but usually once
> every 48 hours.

Could you do a grep through your server logs for "WARNING", to
eliminate the possibility of multiple overlapping searchers causing
the OOM issue?

Are you doing incremental updates?  If so, try lowering your
mergeFactor for the index, or optimize more frequently.  As an index
is incrementally updated, old docs are marked as deleted and new docs
are added.  This leaves "holes" in the document id space which can
increase memory usage.  Both BitSet filters and FieldCache entry sizes
are proportionally related to maxDoc (the maximum internal docid in
the index).

You can see maxDoc from the statistics page... there might be a correlation.


View raw message