Any help appreciated diagnosing this problem, it's been bothering me
for days.
Here's a graph take from the last months memory usage: http://imgur.com/7FnJN
with annoations
- The server was restarted. ElasticSearch is running OpenJDK at this
point. - The app memory balloons and Elastic is restarted.
- Same as before.
- Switched to Suns JRE and now the app memory is under control, but
the swap follows a very similar pattern to that of the memory when
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
Dataset
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
of memory elastic is using.
System
Total memory = 469M
vm.swappiness = 10
Java
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)
Errors
- 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.