# Prevent Elasticsearch from message flood

**URL:** <https://discuss.elastic.co/t/prevent-elasticsearch-from-message-flood/2340>\
**Category:** Elasticsearch\
**Created:** [June 10, 2015, 2:50pm UTC](https://discuss.elastic.co/t/prevent-elasticsearch-from-message-flood/2340 "2015-06-10T14:50:32Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Laines](https://avatars.discourse-cdn.com/v4/letter/l/e495f1/32.png) [@Laines](https://discuss.elastic.co/u/Laines)\
**Post date:** [June 10, 2015, 2:50pm UTC](https://discuss.elastic.co/t/prevent-elasticsearch-from-message-flood/2340/1 "2015-06-10T14:50:32Z")

</div>

Hello

We use Elasticsearch in our elk setup. Logstash is sending the logs via http to Elasticsearch. I wonder is there a way to protect Elasticsearch going down from unexpected high message load?

Cheers  
Chris

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [June 10, 2015, 10:22pm UTC](https://discuss.elastic.co/t/prevent-elasticsearch-from-message-flood/2340/2 "2015-06-10T22:22:25Z")

</div>

Use a broker - redis, kafkfa, MQ.  
Send events to the broker and then to ES, that way they can queue up in the broker if there is an influx and you process them into ES at your own pace.

---

<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, 12:08am UTC](https://discuss.elastic.co/t/prevent-elasticsearch-from-message-flood/2340/3 "2017-07-06T00:08:24Z")

</div>