# Logstash memory consumption and swap memory issues

**URL:** <https://discuss.elastic.co/t/logstash-memory-consumption-and-swap-memory-issues/329456>\
**Category:** Logstash\
**Tags:** docker\
**Created:** [April 5, 2023, 7:36pm UTC](https://discuss.elastic.co/t/logstash-memory-consumption-and-swap-memory-issues/329456 "2023-04-05T19:36:33Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)\
**Post date:** [April 5, 2023, 8:54pm UTC](https://discuss.elastic.co/t/logstash-memory-consumption-and-swap-memory-issues/329456/4 "2023-04-05T20:54:07Z")

</div>

I suggest you get a heap dump when the OOM occurs. See [this thread](https://discuss.elastic.co/t/exception-in-pipeline-worker-and-java-out-of-memory-errors/169916/2) for what to do with the dump. [This thread](https://discuss.elastic.co/t/split-document-into-multiple-document-based-on-condition/316737/9) shows what the report will look like.

---

_[View the full topic](https://discuss.elastic.co/t/logstash-memory-consumption-and-swap-memory-issues/329456)._
