# Logstash Memory leak?

**URL:** <https://discuss.elastic.co/t/logstash-memory-leak/28494>\
**Category:** Logstash\
**Created:** [September 2, 2015, 7:18am UTC](https://discuss.elastic.co/t/logstash-memory-leak/28494 "2015-09-02T07:18:35Z")\
**Posts on this page:** 3\
**Page:** 2

<div class="post-metadata">

**Author:** ![theuntergeek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/theuntergeek/32/44961_2.png) [@theuntergeek](https://discuss.elastic.co/u/theuntergeek)\
**Post date:** [November 25, 2015, 4:58pm UTC](https://discuss.elastic.co/t/logstash-memory-leak/28494/21 "2015-11-25T16:58:36Z")

</div>

> [@Diego\_Parra](#):
>
> it should be matter of days to see the fix in logstash

Yep! We've validated this in internal testing. 2.1.1 will be out soon. We're waiting to see if anything else shakes out from 2.1.0 and put some days of continuous testing in before release.

---

<div class="post-metadata">

**Author:** ![RobT](https://avatars.discourse-cdn.com/v4/letter/r/7ba0ec/32.png) [@RobT](https://discuss.elastic.co/u/RobT)\
**Post date:** [December 10, 2015, 2:11pm UTC](https://discuss.elastic.co/t/logstash-memory-leak/28494/22 "2015-12-10T14:11:19Z")

</div>

Gave 2.1.1 a shot yesterday and happy to report at least in my case it appears to have resolved the issue. I was able to let LS run overnight without restarting the services and the memory usage has remained stable. More time will tell but looks good!

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 5:19am UTC](https://discuss.elastic.co/t/logstash-memory-leak/28494/23 "2017-07-06T05:19:04Z")

</div>



[Previous page](https://discuss.elastic.co/t/logstash-memory-leak/28494.md?page=1)