# Setting Queue Quota for Outputs

**URL:** <https://discuss.elastic.co/t/setting-queue-quota-for-outputs/116738>\
**Category:** Logstash\
**Created:** [January 23, 2018, 7:30pm UTC](https://discuss.elastic.co/t/setting-queue-quota-for-outputs/116738 "2018-01-23T19:30:35Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jorn](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jorn/32/24489_2.png) [@Jorn](https://discuss.elastic.co/u/Jorn)\
**Post date:** [January 23, 2018, 7:30pm UTC](https://discuss.elastic.co/t/setting-queue-quota-for-outputs/116738/1 "2018-01-23T19:30:35Z")

</div>

We have a shared aggregation cluster running Logstash 5.6 that has persistent queues enabled, but as far as we can tell, this resource is shared between all configured outputs. Is there a way for us to configure our outputs in a way to quota how much of the persistent queue that they consume?

i.e. If a destination ES cluster fills up on space, the queue will fill up, and eventually start affecting our S3 export outputs as well. I'd like to restrict the ES export output to 1/2 of the persistent queue as to prevent a scenario where the S3 export is not blocked.

---

<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:** [February 20, 2018, 7:30pm UTC](https://discuss.elastic.co/t/setting-queue-quota-for-outputs/116738/2 "2018-02-20T19:30:49Z")

</div>

Closed on February 20, 2018, 7:30pm UTC

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