# Logstash hold indexes when ES is overloaded

**URL:** <https://discuss.elastic.co/t/logstash-hold-indexes-when-es-is-overloaded/224729>\
**Category:** Logstash\
**Tags:** docker, ilm-index-lifecycle-management\
**Created:** [March 23, 2020, 8:27pm UTC](https://discuss.elastic.co/t/logstash-hold-indexes-when-es-is-overloaded/224729 "2020-03-23T20:27:02Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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:** [March 23, 2020, 10:27pm UTC](https://discuss.elastic.co/t/logstash-hold-indexes-when-es-is-overloaded/224729/2 "2020-03-23T22:27:45Z")

</div>

That's really an elasticsearch question. If elasticsearch indexing slows down there will be back-pressure that will stop logstash sending it more data. It has been answered [here](https://discuss.elastic.co/t/prioritize-search-requests-over-index-requests/109201/2). Not sure if things have changed. I do not run elasticsearch.

---

_[View the full topic](https://discuss.elastic.co/t/logstash-hold-indexes-when-es-is-overloaded/224729)._