# Logstorm after the Logstashserver become for some time unavailable

**URL:** <https://discuss.elastic.co/t/logstorm-after-the-logstashserver-become-for-some-time-unavailable/37782>\
**Category:** Logstash\
**Created:** [December 22, 2015, 6:48pm UTC](https://discuss.elastic.co/t/logstorm-after-the-logstashserver-become-for-some-time-unavailable/37782 "2015-12-22T18:48:04Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![fred23](https://avatars.discourse-cdn.com/v4/letter/f/aca169/32.png) [@fred23](https://discuss.elastic.co/u/fred23)\
**Post date:** [December 22, 2015, 6:48pm UTC](https://discuss.elastic.co/t/logstorm-after-the-logstashserver-become-for-some-time-unavailable/37782/1 "2015-12-22T18:48:04Z")

</div>

Hi,

I have a small setup with 20 clients (logstash-forwarder) and 1 logstash,elasticsearch,kibana server. Now the destination server for my logstash-forwarders becomes for some time (2 days) unavailable. After restart the system, all logstash-forwarder want to send their buffered logs at one time. The logstashserver was overloaded and no logs can be written.  
I Do a workaround, that the logstashserver listen to a new port and then every machine logstash-forwarder was configured by hand to the new port.

Is there another way, to handle this problem?

---

<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:** [December 23, 2015, 1:06am UTC](https://discuss.elastic.co/t/logstorm-after-the-logstashserver-become-for-some-time-unavailable/37782/2 "2015-12-23T01:06:51Z")

</div>

Have a read through [https://www.elastic.co/guide/en/logstash/current/deploying-and-scaling.html](https://www.elastic.co/guide/en/logstash/current/deploying-and-scaling.html), but you probably need to look into a broker to act as a buffer.

---

<div class="post-metadata">

**Author:** ![fred23](https://avatars.discourse-cdn.com/v4/letter/f/aca169/32.png) [@fred23](https://discuss.elastic.co/u/fred23)\
**Post date:** [December 23, 2015, 5:03am UTC](https://discuss.elastic.co/t/logstorm-after-the-logstashserver-become-for-some-time-unavailable/37782/3 "2015-12-23T05:03:22Z")

</div>

Thank you!

Is redis the state of the art as broker?

---

<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:** [December 23, 2015, 5:45am UTC](https://discuss.elastic.co/t/logstorm-after-the-logstashserver-become-for-some-time-unavailable/37782/4 "2015-12-23T05:45:02Z")

</div>

I'd say kafka is a little more advanced than redis these days.

---

<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:17am UTC](https://discuss.elastic.co/t/logstorm-after-the-logstashserver-become-for-some-time-unavailable/37782/5 "2017-07-06T05:17:29Z")

</div>

Closed on July 6, 2017, 5:17am UTC