# ThreadPool Setting not getting applied

**URL:** <https://discuss.elastic.co/t/threadpool-setting-not-getting-applied/94400>\
**Category:** Elasticsearch\
**Created:** [July 24, 2017, 10:14pm UTC](https://discuss.elastic.co/t/threadpool-setting-not-getting-applied/94400 "2017-07-24T22:14:55Z")\
**Posts on this page:** 2\
**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 24, 2017, 10:14pm UTC](https://discuss.elastic.co/t/threadpool-setting-not-getting-applied/94400/1 "2017-07-24T22:14:55Z")

</div>

Question about Elasticsearch version 1.7

I have been trying to use bulk queue size as 1000 using transient setting, which seems to be propogated on all the hosts and I verified by looking at /\_nodes  
thread\_pool:  
bulk:   
type: "fixed"  
min: 2  
max: 2  
queue\_size: "1k"

As our persistent setting is defined as  
threadpool:  
bulk:   
size: "2"  
queue: "8"

Considering transient settings take preference the max bulk queuing on each data node should be 1000, but in our cluster there are nodes running more than 1000 requests getting queued. Any quick ideas on debugging if the setting is defauting to -1 (no bound ) ?

---

<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 21, 2017, 10:15pm UTC](https://discuss.elastic.co/t/threadpool-setting-not-getting-applied/94400/2 "2017-08-21T22:15:01Z")

</div>

Closed on August 21, 2017, 10:15pm UTC

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