# java.lang.OutOfMemoryError: Java heap space on 5.1.2 **URL:** \ **Category:** Elasticsearch\ **Created:** [January 17, 2017, 8:46am UTC](https://discuss.elastic.co/t/java-lang-outofmemoryerror-java-heap-space-on-5-1-2/71830 "2017-01-17T08:46:23Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![tramchamploo](https://avatars.discourse-cdn.com/v4/letter/t/3ec8ea/32.png) [@tramchamploo](https://discuss.elastic.co/u/tramchamploo)\ **Post date:** [January 17, 2017, 8:46am UTC](https://discuss.elastic.co/t/java-lang-outofmemoryerror-java-heap-space-on-5-1-2/71830/1 "2017-01-17T08:46:23Z")
I formerly use 5.1.1 and encountered to this OOM, so I update to 5.1.2 it still happens. ---
**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\ **Post date:** [January 17, 2017, 9:02am UTC](https://discuss.elastic.co/t/java-lang-outofmemoryerror-java-heap-space-on-5-1-2/71830/2 "2017-01-17T09:02:19Z")
That should not be surprising as OOM problems are rarely fixed by minor upgrades. Sounds like you might have to increase the heap or decrease the amount of data. If you supply additional details about your setup we can say more. ---
**Author:** ![jasontedor](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jasontedor/32/66992_2.png) [@jasontedor](https://discuss.elastic.co/u/jasontedor)\ **Post date:** [January 17, 2017, 10:37am UTC](https://discuss.elastic.co/t/java-lang-outofmemoryerror-java-heap-space-on-5-1-2/71830/3 "2017-01-17T10:37:10Z")
> [@magnusbaeck](#): > > That should not be surprising as OOM problems are rarely fixed by minor upgrades. Sounds like you might have to increase the heap or decrease the amount of data. I agree in general. In this case there is [one major stability change](https://github.com/elastic/elasticsearch/commit/faf6e98fd562ed9deb7d253ccea0a95d1bd9429c#diff-905b237960dbc68ab65f59943d6c3de2R71) incorporated into 5.1.2 that should address some of the OOMs that we have been seeing. > [@magnusbaeck](#): > > If you supply additional details about your setup we can say more. Yes, this. A stack trace of where the OOM is coming from would be helpful to know whether or not what you're seeing should have been addressed by the aforementioned change. ---
**Author:** ![tramchamploo](https://avatars.discourse-cdn.com/v4/letter/t/3ec8ea/32.png) [@tramchamploo](https://discuss.elastic.co/u/tramchamploo)\ **Post date:** [January 17, 2017, 10:38am UTC](https://discuss.elastic.co/t/java-lang-outofmemoryerror-java-heap-space-on-5-1-2/71830/4 "2017-01-17T10:38:19Z")
```auto 2017-01-17T16:27:29,548][ERROR][o.e.t.n.Netty4Utils] fatal error on the network layer at org.elasticsearch.transport.netty4.Netty4Utils.maybeDie(Netty4Utils.java:140) at org.elasticsearch.http.netty4.Netty4HttpRequestHandler.exceptionCaught(Netty4HttpRequestHandler.java:76) at io.netty.channel.AbstractChannelHandlerContext.invokeExceptionCaught(AbstractChannelHandlerContext.java:296) at io.netty.channel.AbstractChannelHandlerContext.notifyHandlerException(AbstractChannelHandlerContext.java:861) at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:375) at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:359) at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:351) at org.elasticsearch.http.netty4.pipelining.HttpPipeliningHandler.channelRead(HttpPipeliningHandler.java:66) at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:373) at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:359) at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:351) at io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:102) at io.netty.handler.codec.MessageToMessageCodec.channelRead(MessageToMessageCodec.java:111) at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:373) at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:359) at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:351) at io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:102) at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:373) at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:359) at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:351) at io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:102) at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:373) at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:359) at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:351) at io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:293) at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:267) at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:373) at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:359) at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:351) at io.netty.channel.ChannelInboundHandlerAdapter.channelRead(ChannelInboundHandlerAdapter.java:86) at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:373) [2017-01-17T16:27:25,886][ERROR][o.e.b.ElasticsearchUncaughtExceptionHandler] [node-172.16.105.125] fatal error in thread [Thread-117], exiting java.lang.OutOfMemoryError: Java heap space ``` ---
**Author:** ![jasontedor](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jasontedor/32/66992_2.png) [@jasontedor](https://discuss.elastic.co/u/jasontedor)\ **Post date:** [January 17, 2017, 10:51am UTC](https://discuss.elastic.co/t/java-lang-outofmemoryerror-java-heap-space-on-5-1-2/71830/5 "2017-01-17T10:51:13Z")
Please show the stacktrace under what you just pasted. Namely the stacktrace that is under: ```auto [2017-01-17T16:27:25,886][ERROR][o.e.b.ElasticsearchUncaughtExceptionHandler] [node-172.16.105.125] fatal error in thread [Thread-117], exiting java.lang.OutOfMemoryError: Java heap space ``` ---
**Author:** ![tramchamploo](https://avatars.discourse-cdn.com/v4/letter/t/3ec8ea/32.png) [@tramchamploo](https://discuss.elastic.co/u/tramchamploo)\ **Post date:** [January 18, 2017, 3:00am UTC](https://discuss.elastic.co/t/java-lang-outofmemoryerror-java-heap-space-on-5-1-2/71830/6 "2017-01-18T03:00:46Z")
There's nothing under, and ES process went down. ---
**Author:** ![jasontedor](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jasontedor/32/66992_2.png) [@jasontedor](https://discuss.elastic.co/u/jasontedor)\ **Post date:** [January 18, 2017, 3:42am UTC](https://discuss.elastic.co/t/java-lang-outofmemoryerror-java-heap-space-on-5-1-2/71830/7 "2017-01-18T03:42:43Z")
That the node went down is not unexpected, but there should be a stack trace there (we print it first before shutting the node down). ---
**Author:** ![tramchamploo](https://avatars.discourse-cdn.com/v4/letter/t/3ec8ea/32.png) [@tramchamploo](https://discuss.elastic.co/u/tramchamploo)\ **Post date:** [January 18, 2017, 7:06am UTC](https://discuss.elastic.co/t/java-lang-outofmemoryerror-java-heap-space-on-5-1-2/71830/8 "2017-01-18T07:06:39Z")
I'm sure there's nothing below. ---
**Author:** ![jasontedor](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jasontedor/32/66992_2.png) [@jasontedor](https://discuss.elastic.co/u/jasontedor)\ **Post date:** [January 18, 2017, 8:09am UTC](https://discuss.elastic.co/t/java-lang-outofmemoryerror-java-heap-space-on-5-1-2/71830/9 "2017-01-18T08:09:44Z")
Then there is no information to be gleaned here. ---
**Author:** ![tramchamploo](https://avatars.discourse-cdn.com/v4/letter/t/3ec8ea/32.png) [@tramchamploo](https://discuss.elastic.co/u/tramchamploo)\ **Post date:** [January 18, 2017, 10:03am UTC](https://discuss.elastic.co/t/java-lang-outofmemoryerror-java-heap-space-on-5-1-2/71830/10 "2017-01-18T10:03:13Z")
But version 2 doesn't have this problem with the same amount of data. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [February 15, 2017, 10:03am UTC](https://discuss.elastic.co/t/java-lang-outofmemoryerror-java-heap-space-on-5-1-2/71830/11 "2017-02-15T10:03:37Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.