# Threadpool.bulk.size key ignored

**URL:** <https://discuss.elastic.co/t/threadpool-bulk-size-key-ignored/276124>\
**Category:** Elasticsearch\
**Created:** [June 16, 2021, 10:43am UTC](https://discuss.elastic.co/t/threadpool-bulk-size-key-ignored/276124 "2021-06-16T10:43:40Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![rschirin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rschirin/32/45283_2.png) [@rschirin](https://discuss.elastic.co/u/rschirin)\
**Post date:** [June 16, 2021, 10:43am UTC](https://discuss.elastic.co/t/threadpool-bulk-size-key-ignored/276124/1 "2021-06-16T10:43:40Z")

</div>

Hey there,  
using an old ES version (2.x) I was trying to use a custom configuration regarding threadpool.  
currently, nodes have 8 processors. This value is correctly recognized by ES but when I try to increase it, nothing happens.  
I specified

```auto
threadpool.bulk.type: fixed
threadpool.bulk.size: 16

```

into every `elasticsearch.yml` file and then I have fully restarted the cluster.  
I tried also to use the dynamic updates of cluster settings withoud any result.  
The threadpool size is still capped to 8 and I got this log message:

`requested thread pool size [16] for [bulk] is too large; setting to maximum [8] instead`

The only way to get it is to specify

`processor: 16`

in the `elasticsearch.yml` but I would like to avoid this way. is this the only way to do that?  
I saw also [github issue](https://github.com/elastic/elasticsearch/issues/15582). If this is correct, this scenario should be highlighted in the official doc (also the current 7.x).

Anyone can help or address me?

---

<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:** [June 17, 2021, 1:14am UTC](https://discuss.elastic.co/t/threadpool-bulk-size-key-ignored/276124/2 "2021-06-17T01:14:34Z")

</div>

> [@rschirin](#):
>
> in the `elasticsearch.yml` but I would like to avoid this way. is this the only way to do that?

Yep, there's not a lot of point in having more process threads for a given pool than there is CPU threads. You're really just moving the problem elsewhere.

---

<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:** [July 15, 2021, 1:15am UTC](https://discuss.elastic.co/t/threadpool-bulk-size-key-ignored/276124/3 "2021-07-15T01:15:28Z")

</div>

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