# Queue.drain: true not being respected

**URL:** <https://discuss.elastic.co/t/queue-drain-true-not-being-respected/151073>\
**Category:** Logstash\
**Created:** [October 4, 2018, 3:55pm UTC](https://discuss.elastic.co/t/queue-drain-true-not-being-respected/151073 "2018-10-04T15:55:47Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![cmendelson](https://avatars.discourse-cdn.com/v4/letter/c/848f3c/32.png) [@cmendelson](https://discuss.elastic.co/u/cmendelson)\
**Post date:** [October 4, 2018, 3:55pm UTC](https://discuss.elastic.co/t/queue-drain-true-not-being-respected/151073/1 "2018-10-04T15:55:47Z")

</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 (`service 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:** [November 1, 2018, 3:55pm UTC](https://discuss.elastic.co/t/queue-drain-true-not-being-respected/151073/2 "2018-11-01T15:55:48Z")

</div>

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