# Change elasticsearch threadpool index queue\_size

**URL:** <https://discuss.elastic.co/t/change-elasticsearch-threadpool-index-queue-size/105006>\
**Category:** Elasticsearch\
**Created:** [October 24, 2017, 7:49am UTC](https://discuss.elastic.co/t/change-elasticsearch-threadpool-index-queue-size/105006 "2017-10-24T07:49:35Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![patricia022](https://avatars.discourse-cdn.com/v4/letter/p/7c8e57/32.png) [@patricia022](https://discuss.elastic.co/u/patricia022)\
**Post date:** [October 24, 2017, 7:49am UTC](https://discuss.elastic.co/t/change-elasticsearch-threadpool-index-queue-size/105006/1 "2017-10-24T07:49:35Z")

</div>

Hi everyone,

I would like to ask if I can modify the index queue\_size from 200 to 1000 using API calls.

"index": {  
"type": "fixed",  
"min": 2,  
"max": 2,  
"queue\_size": 200  
}

Thanks

---

<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:** [October 24, 2017, 7:50am UTC](https://discuss.elastic.co/t/change-elasticsearch-threadpool-index-queue-size/105006/2 "2017-10-24T07:50:34Z")

</div>

No you cannot, they are a static setting.

Also, why do you want to do this?

---

<div class="post-metadata">

**Author:** ![patricia022](https://avatars.discourse-cdn.com/v4/letter/p/7c8e57/32.png) [@patricia022](https://discuss.elastic.co/u/patricia022)\
**Post date:** [October 24, 2017, 7:52am UTC](https://discuss.elastic.co/t/change-elasticsearch-threadpool-index-queue-size/105006/3 "2017-10-24T07:52:07Z")

</div>

I'm currently doing some load testing and I encountered this error

{"error":{"root\_cause":[{"type":"es\_rejected\_execution\_exception","reason":"rejected execution of org.elasticsearch.transport.TransportService$4@7868ca6f on EsThreadPoolExecutor[index, queue capacity = 200, org.elasticsearch.common.util.concurrent.EsThreadPoolExecutor@7f817344[Running, pool size = 1, active threads = 1, queued tasks = 203, completed tasks = 668181]]"}],"type":"es\_rejected\_execution\_exception","reason":"rejected execution of org.elasticsearch.transport.TransportService$4@7868ca6f on EsThreadPoolExecutor[index, queue capacity = 200, org.elasticsearch.common.util.concurrent.EsThreadPoolExecutor@7f817344[Running, pool size = 1, active threads = 1, queued tasks = 203, completed tasks = 668181]]"},"status":429}

Any thoughts on how I can fix this?

---

<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:** [October 24, 2017, 7:52am UTC](https://discuss.elastic.co/t/change-elasticsearch-threadpool-index-queue-size/105006/4 "2017-10-24T07:52:42Z")

</div>

The best thing I can do is point you to this post - [Any idea what these errors mean version 2.4.2](https://discuss.elastic.co/t/any-idea-what-these-errors-mean-version-2-4-2/70690/5)

---

<div class="post-metadata">

**Author:** ![patricia022](https://avatars.discourse-cdn.com/v4/letter/p/7c8e57/32.png) [@patricia022](https://discuss.elastic.co/u/patricia022)\
**Post date:** [October 24, 2017, 7:56am UTC](https://discuss.elastic.co/t/change-elasticsearch-threadpool-index-queue-size/105006/5 "2017-10-24T07:56:16Z")

</div>

I've read the thread on the link you sent.  
The other one suggested to try bulk instead

May i know how I can implement in bulk?

[https://www.elastic.co/guide/en/elasticsearch/reference/2.4/modules-threadpool.html](https://www.elastic.co/guide/en/elasticsearch/reference/2.4/modules-threadpool.html)

---

<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:** [October 24, 2017, 6:09pm UTC](https://discuss.elastic.co/t/change-elasticsearch-threadpool-index-queue-size/105006/6 "2017-10-24T18:09:58Z")

</div>

Modifying the indexing queue size generally just makes the problem worse as more data need to be held in memory. It sounds like you are overwhelming the cluster. What is the specification of your cluster and how much data are you throwing at it concurrently? How many shards are you actively indexing into?

---

<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:** [November 21, 2017, 6:10pm UTC](https://discuss.elastic.co/t/change-elasticsearch-threadpool-index-queue-size/105006/7 "2017-11-21T18:10:05Z")

</div>

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