# Java heap space issue
**URL:** https://discuss.elastic.co/t/java-heap-space-issue/90816
**Category:** Elasticsearch
**Created:** [June 26, 2017, 11:16am UTC](https://discuss.elastic.co/t/java-heap-space-issue/90816 "2017-06-26T11:16:56Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@vijayramachandran](https://discuss.elastic.co/u/vijayramachandran)
#### Post date: [June 26, 2017, 11:16am UTC](https://discuss.elastic.co/t/java-heap-space-issue/90816/1 "2017-06-26T11:16:57Z")
Hello there!
All of a sudden today, one of the elastic nodes had come down due to the below issue,
What could be the possible value that I can bump it up to resolve this issue?
```
> [2017-06-26T13:00:47,081][TRACE][o.e.i.e.Engine] [ccncmu24.de.db.com-node2] [search-sside][4] committing writer with translog id [29] and sync id [null]
> [2017-06-26T13:00:47,081][TRACE][o.e.i.b.request] [request] Adjusted breaker by [-16440] bytes, now [32880]
> [2017-06-26T13:00:47,053][WARN][o.e.x.s.t.n.SecurityNetty4Transport] [ccncmu24.de.db.com-node2] exception caught on transport layer [[id: 0x7d5a964e, L:/10.216.62.22:9302 - R:/10.216.60.217:38220]], closing connection
> io.netty.handler.codec.DecoderException: java.lang.OutOfMemoryError: Java heap space
> at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:442) ~[netty-codec-4.1.7.Final.jar:4.1.7.Final]
> at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:248) ~[netty-codec-4.1.7.Final.jar:4.1.7.Final]
```
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 24, 2017, 11:16am UTC](https://discuss.elastic.co/t/java-heap-space-issue/90816/2 "2017-07-24T11:16:59Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.