# ES stack trace does not reflect altered thread pool configuration

**URL:** <https://discuss.elastic.co/t/es-stack-trace-does-not-reflect-altered-thread-pool-configuration/164757>\
**Category:** Elasticsearch\
**Created:** [January 18, 2019, 9:02am UTC](https://discuss.elastic.co/t/es-stack-trace-does-not-reflect-altered-thread-pool-configuration/164757 "2019-01-18T09:02:27Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![jwistrom](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jwistrom/32/41798_2.png) [@jwistrom](https://discuss.elastic.co/u/jwistrom)\
**Post date:** [January 18, 2019, 9:02am UTC](https://discuss.elastic.co/t/es-stack-trace-does-not-reflect-altered-thread-pool-configuration/164757/1 "2019-01-18T09:02:27Z")

</div>

Hi  
We have recently updated to ES 6.5.3 and changed the default configuration accordingly:

```
thread_pool.search.queue_size: 8000
thread_pool.search.size: 35

```

When querying this at runtime we get:

```auto
   "thread_pool" : {
          "search" : {
            "queue_size" : "8000",
            "size" : "35"
          }

```

...so the configuration modifications take effect. The problem is that when we increase the rate of our querying we get this stack trace:

```auto
Caused by: org.elasticsearch.common.util.concurrent.EsRejectedExecutionException: rejected execution 
of org.elasticsearch.common.util.concurrent.TimedRunnable@17f348a3 on 
QueueResizingEsThreadPoolExecutor[name = thu-match-es4/search, queue capacity = 1000, min queue 
capacity = 1000, max queue capacity = 1000, frame size = 2000, targeted response rate = 1s, task 
execution EWMA = 514.2micros, adjustment amount = 50, 
org.elasticsearch.common.util.concurrent.QueueResizingEsThreadPoolExecutor@31dbc67a[Running, 
pool size = 25, active threads = 20, queued tasks = 999, completed tasks = 2878951156]]

```

My question is, why does the stack trace not reflect our modified configuration? Is there a problem in 6.5.3 or have we set the configuration incorrectly?

Regards  
Johan

---

<div class="post-metadata">

**Author:** ![danielmitterdorfer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/danielmitterdorfer/32/110510_2.png) [@danielmitterdorfer](https://discuss.elastic.co/u/danielmitterdorfer)\
**Post date:** [January 25, 2019, 1:42pm UTC](https://discuss.elastic.co/t/es-stack-trace-does-not-reflect-altered-thread-pool-configuration/164757/2 "2019-01-25T13:42:21Z")

</div>

Hi,

how many nodes does your cluster have? Did you apply this setting to all nodes?

Daniel

---

<div class="post-metadata">

**Author:** ![jwistrom](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jwistrom/32/41798_2.png) [@jwistrom](https://discuss.elastic.co/u/jwistrom)\
**Post date:** [January 29, 2019, 1:25pm UTC](https://discuss.elastic.co/t/es-stack-trace-does-not-reflect-altered-thread-pool-configuration/164757/3 "2019-01-29T13:25:16Z")

</div>

We have 4 nodes and the setting was applied to all nodes

---

<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 26, 2019, 1:25pm UTC](https://discuss.elastic.co/t/es-stack-trace-does-not-reflect-altered-thread-pool-configuration/164757/4 "2019-02-26T13:25:19Z")

</div>

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