OOM Java heapspace on ES1.1.1 cluster

I have an Elasticsearch 1.1.1 cluster with two nodes configured heap of 18G each. (RAM on each node is 32G) With 6 Shards and one replica for each shard.

There is only one index in our cluster. Cluster health looks Green. There are 200millon documents per node (with size of 150GB/node).

System is encountering the OOM issue (java.lang.OutOfMemoryError: Java heap space).

It has been noticed that the instances of org.apache.lucene.search.TopFieldCollector$OneComparatorNonScoringCollector is occupying most of the heapspace (around 45%)

I am new to ES. Could someone guide (or comment/insights) on situation on the
OOM issue ?

Yes. Upgrade !

At least to 1.7 (not supported anymore though), to 2.4 (better) or to 5.2 (even better)

2 Likes

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.