Try to find out which kind of memory the heap is piling up (Perma Old New). Tomcat is a notorious PermaGen leaker.
-------- Original Message --------
Subject: Re: Memory problems
From: lmader <email@example.com>
Date: Wed, July 06, 2011 4:52 pm
To: users <firstname.lastname@example.org>
We are seeing the same issue. That is, running elasticsearch server
on linux with the sun jdk, the application memory seems constant, but
the swap memory steadily grows over the course of a week or so, until
we run out of swap space.
Additionally, I believe that our elastic client that runs in a Tomcat
webapp is leaking non-heap memory. After a period of time, the
process memory (but not the JVM memory) starts to grow steadily until
we have to restart the tomcat server. We never get a java "out of
memory" error, instead the java process eventually consumes all of
We have been doing our best to isolate this, and it really does seem
to be the elastic client that is leaking the memory. Perhaps the
sever side swap memory growth is related.
I think we need help with this one.
On Jun 20, 11:25 am, Mathew Davies <thepixeldevelo...@googlemail.com>
> Any help appreciated diagnosing this problem, it's been bothering me
> for days.
> Here's a graph take from the last monthsmemoryusage:http://imgur.com/7FnJN
> with annoations
> 1. The server was restarted. ElasticSearch is running OpenJDK at this
> 2. The appmemoryballoons and Elastic is restarted.
> 3. Same as before.
> 4. Switched to Suns JRE and now the appmemoryis under control, but
> the swap follows a very similar pattern to that of thememorywhen
> using OpenJDK
> ElasticSearch configuration as from no. 4 on the graph.
> bin/service/elasticsearch.conf -http://pastie.org/private/h3johakoudfe8m8wzojg
> config/elasticsearch.yaml -http://pastie.org/private/aarhchbycpax8lwczjswa
> Version: 0.16.2
> Around 3,000 entries with 4 string fields, 2 ints, 1 float and a date
> time field. I would expect such a small data set to not use the amount
> ofmemoryelastic is using.
> Totalmemory= 469M
> vm.swappiness = 10
> java version "1.6.0_24"
> Java(TM) SE Runtime Environment (build 1.6.0_24-b07)
> Java HotSpot(TM) Client VM (build 19.1-b02, mixed mode, sharing)
> * This one is happening ever few hours: Jun 20 19:12:25 *** kernel:
> swapper: page allocation failure. order:5, mode:0x20
> * A frequent search term error I'm not too worried about, but could be
> a contributor:http://pastie.org/private/ceuoczbn65natwg6epm2a
> If any more information is required then I'd be happy to help out.
> Thanks for reading.