# Nodes threadpool settings

**URL:** <https://discuss.elastic.co/t/nodes-threadpool-settings/91694>\
**Category:** Elasticsearch\
**Created:** [July 3, 2017, 10:04pm UTC](https://discuss.elastic.co/t/nodes-threadpool-settings/91694 "2017-07-03T22:04:57Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dhara\_Desai](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dhara_desai/32/15760_2.png) [@Dhara\_Desai](https://discuss.elastic.co/u/Dhara_Desai)\
**Post date:** [July 3, 2017, 10:04pm UTC](https://discuss.elastic.co/t/nodes-threadpool-settings/91694/1 "2017-07-03T22:04:58Z")

</div>

We run elasticsearch 1.7 and the cluster has around 342 nodes.  
I am trying to set the search threadpool size to 14 and the setting is applied correctly, meaning GET /\_cluster/settings reflects the new values but the in /\_nodes/stats the vaue of "thread\_pool.search.threads" is defaulted to 13 form majority of the host. Only around a 100 hosts are getting the new value (14)

Any points on how can I debug this issue? seems like nodes are not pooling the latest config from master

---

<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:** [July 3, 2017, 11:23pm UTC](https://discuss.elastic.co/t/nodes-threadpool-settings/91694/2 "2017-07-03T23:23:29Z")

</div>

What's pending tasks on some of the nodes that haven't applied it look like?

> [@Dhara\_Desai](#):
>
> We run elasticsearch 1.7 and the cluster has around 342 nodes.

You should really upgrade. 2.2 is nearly EOL!

---

<div class="post-metadata">

**Author:** ![Dhara\_Desai](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dhara_desai/32/15760_2.png) [@Dhara\_Desai](https://discuss.elastic.co/u/Dhara_Desai)\
**Post date:** [July 17, 2017, 6:37pm UTC](https://discuss.elastic.co/t/nodes-threadpool-settings/91694/3 "2017-07-17T18:37:24Z")

</div>

Hey Mark, I figured out the issue. It was related to the new plugin we integrated for elasticsearch metrics. And yes, Upgrading is the plan !

---

<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:** [August 14, 2017, 6:37pm UTC](https://discuss.elastic.co/t/nodes-threadpool-settings/91694/4 "2017-08-14T18:37:48Z")

</div>

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