# OOM error with logstash S3 input over large data

**URL:** <https://discuss.elastic.co/t/oom-error-with-logstash-s3-input-over-large-data/214>\
**Category:** Logstash\
**Created:** [May 5, 2015, 1:00pm UTC](https://discuss.elastic.co/t/oom-error-with-logstash-s3-input-over-large-data/214 "2015-05-05T13:00:35Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![vangap](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vangap/32/44927_2.png) [@vangap](https://discuss.elastic.co/u/vangap)\
**Post date:** [May 5, 2015, 1:00pm UTC](https://discuss.elastic.co/t/oom-error-with-logstash-s3-input-over-large-data/214/1 "2015-05-05T13:00:35Z")

</div>

I have Elasticsearch, Logstash running on a m3.xlarge.  
ES 1.5.2  
Logstash 1.5.0-rc3  
ArchLinux

I  
am trying to index 3 months log data into ELK, but after some time I  
see that kernel is killing the processes because of an OOM error. [http://pastie.org/10155132](http://pastie.org/10155132)  
I looked at the memory metrics, which was constant around 70% (with 50% mlocked by ES).

After few minutes of starting logstash, OOM kills ES.

I noticed that /tmp/logstash size is 5.5 GB. logstash ran fine for some time when I first started indexing.  
Is logstash trying to bulk index all these files?

How do I avoid this? can I throttles this some how? If I change this temporary location, will that be of any help?

Thanks.

---

<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:40am UTC](https://discuss.elastic.co/t/oom-error-with-logstash-s3-input-over-large-data/214/2 "2017-07-06T05:40:16Z")

</div>