# ES 7.5.0 gets OOM
**URL:** https://discuss.elastic.co/t/es-7-5-0-gets-oom/212501
**Category:** Elasticsearch
**Created:** [December 19, 2019, 1:46pm UTC](https://discuss.elastic.co/t/es-7-5-0-gets-oom/212501 "2019-12-19T13:46:52Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@michalz](https://discuss.elastic.co/u/michalz)
#### Post date: [December 19, 2019, 1:46pm UTC](https://discuss.elastic.co/t/es-7-5-0-gets-oom/212501/1 "2019-12-19T13:46:52Z")
# I am new to ELK and would like to use ES in connection with Logstash. Logstash is supposed to put around 15MB of data to ES. However my ES (which is run in Docker) does not behave stable. After about few minutes the container is down and the last logs indicate that there are memory problems: {"type": "server", "timestamp": "2019-12-19T13:38:21,613Z", "level": "WARN", "component": "o.e.m.j.JvmGcMonitorService", "cluster.name": "elasticsearch", "node.name": "elasticsearch", "message": "[gc][young][286][71] duration [3s], collections [1]/[1.3s], total [3s]/[7.2s], memory [325.8mb]-\>[341mb]/[990.7mb], all\_pools {[young] [251.8mb]-\>[4mb]/[266.2mb]}{[survivor] [4.5mb]-\>[5.5mb]/[33.2mb]}{[old] [71.6mb]-\>[71.6mb]/[691.2mb]}", "cluster.uuid": "gl37Eo6uROmeNink4VhWeg", "node.id": "69Z2EvjeQiidUzkfFtUz4A" } {"type": "server", "timestamp": "2019-12-19T13:38:22,113Z", "level": "WARN", "component": "o.e.m.j.JvmGcMonitorService", "cluster.name": "elasticsearch", "node.name": "elasticsearch", "message": "[gc][286] overhead, spent [3s] collecting in the last [1.3s]", "cluster.uuid": "gl37Eo6uROmeNink4VhWeg", "node.id": "69Z2EvjeQiidUzkfFtUz4A" } {"type": "server", "timestamp": "2019-12-19T13:39:50,226Z", "level": "INFO", "component": "o.e.x.m.p.NativeController", "cluster.name": "elasticsearch", "node.name": "elasticsearch", "message": "Native controller process has stopped - no new native processes can be started", "cluster.uuid": "gl37Eo6uROmeNink4VhWeg", "node.id": "69Z2EvjeQiidUzkfFtUz4A" }
I am not quite sure what is going on because I run ES with custom jvm.options ie.
-Xms1g
-Xmx2g
and this should be enough.
Could anyone help me out in determining what is going on, where to investigate? Thanks
---
### Author:  [@Bernt\_Rostad](https://discuss.elastic.co/u/Bernt_Rostad)
#### Post date: [December 19, 2019, 2:09pm UTC](https://discuss.elastic.co/t/es-7-5-0-gets-oom/212501/2 "2019-12-19T14:09:29Z")
It looks like Elasticsearch is running out of memory and that it only has 1 GB of Java Heap Size, so you need to increase it.
> [@michalz](#):
>
> I am not quite sure what is going on because I run ES with custom jvm.options ie.
> -Xms1g
> -Xmx2g
You need to set **both** -Xms and -Xmx to the **same** value, for instance
```
-Xms2g
-Xmx2g
```
or perhaps even higher, if you keep getting OOM exceptions. I typically run with 8 GB Java Heap Size on my data nodes.
---
### Author:  [@michalz](https://discuss.elastic.co/u/michalz)
#### Post date: [December 19, 2019, 3:29pm UTC](https://discuss.elastic.co/t/es-7-5-0-gets-oom/212501/3 "2019-12-19T15:29:00Z")
thanks. when both are the same, ES works fine 🙂
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [January 16, 2020, 3:29pm UTC](https://discuss.elastic.co/t/es-7-5-0-gets-oom/212501/4 "2020-01-16T15:29:09Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.