# OOM Java heapspace on ES1.1.1 cluster **URL:** \ **Category:** Elasticsearch\ **Created:** [March 16, 2017, 12:25pm UTC](https://discuss.elastic.co/t/oom-java-heapspace-on-es1-1-1-cluster/78854 "2017-03-16T12:25:37Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![krckumar](https://avatars.discourse-cdn.com/v4/letter/k/cdc98d/32.png) [@krckumar](https://discuss.elastic.co/u/krckumar)\ **Post date:** [March 16, 2017, 12:25pm UTC](https://discuss.elastic.co/t/oom-java-heapspace-on-es1-1-1-cluster/78854/1 "2017-03-16T12:25:37Z")
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 ? ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [March 16, 2017, 2:39pm UTC](https://discuss.elastic.co/t/oom-java-heapspace-on-es1-1-1-cluster/78854/2 "2017-03-16T14:39:04Z")
Yes. Upgrade ! At least to 1.7 (not supported anymore though), to 2.4 (better) or to 5.2 (even better) ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [April 13, 2017, 2:39pm UTC](https://discuss.elastic.co/t/oom-java-heapspace-on-es1-1-1-cluster/78854/3 "2017-04-13T14:39:03Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.