# Is there a queue between filter and output in logstash?

**URL:** <https://discuss.elastic.co/t/is-there-a-queue-between-filter-and-output-in-logstash/296682>\
**Category:** Logstash\
**Created:** [February 9, 2022, 6:58am UTC](https://discuss.elastic.co/t/is-there-a-queue-between-filter-and-output-in-logstash/296682 "2022-02-09T06:58:09Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![JohnPhilip](https://avatars.discourse-cdn.com/v4/letter/j/57b2e6/32.png) [@JohnPhilip](https://discuss.elastic.co/u/JohnPhilip)\
**Post date:** [February 9, 2022, 6:58am UTC](https://discuss.elastic.co/t/is-there-a-queue-between-filter-and-output-in-logstash/296682/1 "2022-02-09T06:58:09Z")

</div>

As the [Execution Model](https://www.elastic.co/guide/en/logstash/current/execution-model.html) mentioned,

```auto
By default, Logstash uses in-memory bounded queues between pipeline stages (input → filter and filter → output) to buffer events.

```

but there is another saying in [Memory queue](https://www.elastic.co/guide/en/logstash/current/memory-queue.html#memory-queue),

```auto
By default, Logstash uses in-memory bounded queues between pipeline stages (inputs → pipeline workers) to buffer events.

```

And I've seen something that logstash optimized the model, combine filter and output to one thread, So is the statement in [Execution Model](https://www.elastic.co/guide/en/logstash/current/execution-model.html) is wrong? there is only one queue between input and pipeline workers?

---

<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:** [March 9, 2022, 6:58am UTC](https://discuss.elastic.co/t/is-there-a-queue-between-filter-and-output-in-logstash/296682/2 "2022-03-09T06:58:34Z")

</div>

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