# Lots of disconnected logs and then OOM

**URL:** <https://discuss.elastic.co/t/lots-of-disconnected-logs-and-then-oom/177758>\
**Category:** Elasticsearch\
**Created:** [April 21, 2019, 2:39pm UTC](https://discuss.elastic.co/t/lots-of-disconnected-logs-and-then-oom/177758 "2019-04-21T14:39:09Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [April 21, 2019, 3:26pm UTC](https://discuss.elastic.co/t/lots-of-disconnected-logs-and-then-oom/177758/2 "2019-04-21T15:26:12Z")

</div>

I think you already asked this, or something very like it, here:

> [@Es node suddenly OOM with "fatal error on the network layer"](https://discuss.elastic.co/t/es-node-suddenly-oom-with-fatal-error-on-the-network-layer/177746/1):
>
> hi, ES version: 5.4.3 java version: 1.8.0\_162 ES was running normally and GC is normal too. But one node suddenly OOM with "fatal error on the network layer" logs link: Does anyone meet this before? How to debug this problem ? Thank you in advance!

As before:

> [@Es node suddenly OOM with "fatal error on the network layer"](https://discuss.elastic.co/t/es-node-suddenly-oom-with-fatal-error-on-the-network-layer/177746/2):
>
> By default Elasticsearch will write a heap dump when it encounters an OutOfMemoryError. The best thing to do is to open this heap dump (e.g. in [MAT](https://www.eclipse.org/mat/)) and investigate what was using all the heap.

If you need help investigating your heap dump then you can ask more detailed questions here of course.

---

_[View the full topic](https://discuss.elastic.co/t/lots-of-disconnected-logs-and-then-oom/177758)._