# Increase max queue capacity?

**URL:** <https://discuss.elastic.co/t/increase-max-queue-capacity/132195>\
**Category:** Elasticsearch\
**Created:** [May 16, 2018, 5:57pm UTC](https://discuss.elastic.co/t/increase-max-queue-capacity/132195 "2018-05-16T17:57:48Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Wanderer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/wanderer/32/55140_2.png) [@Wanderer](https://discuss.elastic.co/u/Wanderer)\
**Post date:** [May 16, 2018, 5:57pm UTC](https://discuss.elastic.co/t/increase-max-queue-capacity/132195/1 "2018-05-16T17:57:49Z")

</div>

Running 6.2.4 We are getting this error in one of our dashboards.

rejected execution of org.elasticsearch.common.util.concurrent.TimedRunnable@55490381 on QueueResizingEsThreadPoolExecutor[name = es-01/search, queue capacity = 1000, min queue capacity = 1000, max queue capacity = 1000, frame size = 2000, targeted response rate = 1s, task execution EWMA = 27.3ms, adjustment amount = 50, org.elasticsearch.common.util.concurrent.QueueResizingEsThreadPoolExecutor@450c7b3f[Running, pool size = 10, active threads = 10, queued tasks = 1392, completed tasks = 805972]]

What is the way to increase the queue capacity? We cannot add more nodes at the moment.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [May 17, 2018, 6:34am UTC](https://discuss.elastic.co/t/increase-max-queue-capacity/132195/2 "2018-05-17T06:34:27Z")

</div>

This will only increase the pressure on your cluster.

Why is it creating such a high use of the threadpools? Do you have Monitoring enabled?

---

<div class="post-metadata">

**Author:** ![Wanderer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/wanderer/32/55140_2.png) [@Wanderer](https://discuss.elastic.co/u/Wanderer)\
**Post date:** [May 17, 2018, 1:52pm UTC](https://discuss.elastic.co/t/increase-max-queue-capacity/132195/3 "2018-05-17T13:52:38Z")

</div>

We have one dashboard that causes this. The visualization on their own do work fine.

Monitoring enabled? What do you mean?

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [May 17, 2018, 2:14pm UTC](https://discuss.elastic.co/t/increase-max-queue-capacity/132195/4 "2018-05-17T14:14:42Z")

</div>

How many visualisations does this dashboard have? How many shards does it address?

---

<div class="post-metadata">

**Author:** ![Wanderer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/wanderer/32/55140_2.png) [@Wanderer](https://discuss.elastic.co/u/Wanderer)\
**Post date:** [May 17, 2018, 2:31pm UTC](https://discuss.elastic.co/t/increase-max-queue-capacity/132195/5 "2018-05-17T14:31:43Z")

</div>

15 visualizations. Screenshot shows the current shards. Not sure why metricbeat is only showing 1. Most of the visualiztions with issues are metricbeat.  
 ![image](https://us1.discourse-cdn.com/elastic/original/3X/4/4/44b1778159474f992f8462f0a9f536fdc7f6e4ef.png)

---

<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:** [June 14, 2018, 2:31pm UTC](https://discuss.elastic.co/t/increase-max-queue-capacity/132195/6 "2018-06-14T14:31:46Z")

</div>

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