# Logstash queue.drain: true setting not being honored

**URL:** https://discuss.elastic.co/t/logstash-queue-drain-true-setting-not-being-honored/301460
**Category:** Logstash
**Created:** [April 4, 2022, 7:19am UTC](https://discuss.elastic.co/t/logstash-queue-drain-true-setting-not-being-honored/301460 "2022-04-04T07:19:33Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![kannan\_raj](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kannan_raj/32/63201_2.png) [@kannan\_raj](https://discuss.elastic.co/u/kannan_raj)
#### Post date: [April 4, 2022, 7:19am UTC](https://discuss.elastic.co/t/logstash-queue-drain-true-setting-not-being-honored/301460/1 "2022-04-04T07:19:33Z")

</div>

I've enabled the `queue.drain: true` setting on one of my logstash instances which has a persistent queue.  
The behavior I would expect is that when I stop the logstash process ( `systemctl logstash stop` ) the page files would be drained, processed and flushed.  
Instead what I see is a pagefile that seems to have data in it ( `wc` shows several thousand lines), and when I tail the file there is what appears to be serialized input data.

Is this the expected behavior for queue.drain, or am I missing something?

---

<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 2, 2022, 7:20am UTC](https://discuss.elastic.co/t/logstash-queue-drain-true-setting-not-being-honored/301460/2 "2022-05-02T07:20:03Z")

</div>

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