# Log stash behavior when output plug-in not reachable

**URL:** <https://discuss.elastic.co/t/log-stash-behavior-when-output-plug-in-not-reachable/331376>\
**Category:** Logstash\
**Created:** [April 30, 2023, 6:14pm UTC](https://discuss.elastic.co/t/log-stash-behavior-when-output-plug-in-not-reachable/331376 "2023-04-30T18:14:02Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![eth](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/eth/32/120441_2.png) [@eth](https://discuss.elastic.co/u/eth)\
**Post date:** [April 30, 2023, 6:14pm UTC](https://discuss.elastic.co/t/log-stash-behavior-when-output-plug-in-not-reachable/331376/1 "2023-04-30T18:14:03Z")

</div>

I am using logstash 7 with syslog as output plugin. The syslog server is not reachable for a quite a long time and persistent queue is growing as expected to the limit. But the persistent queue data size is growing beyond the max\_queue size limit and filling up the entire disk space. The page and check point files count is kept on increasing. Is this expected behavior ? Is not the log stash not reads any input data when the max\_queue\_size\_in\_bytes limit is reached and out put plug-in is not reachable ? I am using beats and kafka as input plug-ins and syslog as output plug-in.

---

<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:** [May 28, 2023, 6:14pm UTC](https://discuss.elastic.co/t/log-stash-behavior-when-output-plug-in-not-reachable/331376/2 "2023-05-28T18:14:32Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.