# Filebeat recovery from ES disconnect

**URL:** <https://discuss.elastic.co/t/filebeat-recovery-from-es-disconnect/105143>\
**Category:** Beats\
**Created:** [October 25, 2017, 3:08am UTC](https://discuss.elastic.co/t/filebeat-recovery-from-es-disconnect/105143 "2017-10-25T03:08:42Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![ChaosMTA](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chaosmta/32/23372_2.png) [@ChaosMTA](https://discuss.elastic.co/u/ChaosMTA)\
**Post date:** [October 25, 2017, 3:08am UTC](https://discuss.elastic.co/t/filebeat-recovery-from-es-disconnect/105143/1 "2017-10-25T03:08:42Z")

</div>

Hi there,

I wasn't able to find much information in the documentation about how Filebeat reacts when the elasticsearch output server is unavailable for a period of time.

Does it give up on any logs it tries to send? An interruption should not be more than 1 hour where Filebeat cannot reach the elasticsearch instance but I was wondering what if.

Thanks

---

<div class="post-metadata">

**Author:** ![steffens](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/steffens/32/79630_2.png) [@steffens](https://discuss.elastic.co/u/steffens)\
**Post date:** [October 25, 2017, 12:48pm UTC](https://discuss.elastic.co/t/filebeat-recovery-from-es-disconnect/105143/2 "2017-10-25T12:48:35Z")

</div>

Filebeat provides send-at-least-once. That is, it will retry infinitely until events are ACKed by Elasticsearch. Retry is subject to exponential backoff, starting at 1s, up to max 60s.

---

<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:** [November 15, 2017, 3:09am UTC](https://discuss.elastic.co/t/filebeat-recovery-from-es-disconnect/105143/3 "2017-11-15T03:09:03Z")

</div>

This topic was automatically closed after 21 days. New replies are no longer allowed.