# Rejected thread pool **URL:** \ **Category:** Elasticsearch\ **Created:** [December 18, 2019, 7:57pm UTC](https://discuss.elastic.co/t/rejected-thread-pool/212395 "2019-12-18T19:57:46Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![jdambly](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jdambly/32/44286_2.png) [@jdambly](https://discuss.elastic.co/u/jdambly)\ **Post date:** [December 18, 2019, 7:57pm UTC](https://discuss.elastic.co/t/rejected-thread-pool/212395/1 "2019-12-18T19:57:46Z")
I am getting rejected thread pools on just one node, how can I resolve this? ``` node_name name active rejected completed elastic-es-data-2 analyze 0 0 0 elastic-es-data-2 ccr 0 0 0 elastic-es-data-2 data_frame_indexing 0 0 0 elastic-es-data-2 fetch_shard_started 0 0 0 elastic-es-data-2 fetch_shard_store 0 0 1 elastic-es-data-2 flush 0 0 144 elastic-es-data-2 force_merge 0 0 0 elastic-es-data-2 generic 0 0 14745 elastic-es-data-2 get 0 0 6 elastic-es-data-2 listener 0 0 14 elastic-es-data-2 management 1 0 29589 elastic-es-data-2 ml_datafeed 0 0 0 elastic-es-data-2 ml_job_comms 0 0 0 elastic-es-data-2 ml_utility 0 0 0 elastic-es-data-2 refresh 0 0 17059 elastic-es-data-2 rollup_indexing 0 0 0 elastic-es-data-2 search 0 0 2015 elastic-es-data-2 search_throttled 0 0 0 elastic-es-data-2 security-token-key 0 0 0 elastic-es-data-2 snapshot 0 0 0 elastic-es-data-2 warmer 0 0 0 elastic-es-data-2 watcher 0 0 0 elastic-es-data-2 write 1 15129 50417 ``` ---
**Author:** ![sebgl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sebgl/32/48702_2.png) [@sebgl](https://discuss.elastic.co/u/sebgl)\ **Post date:** [December 19, 2019, 7:43am UTC](https://discuss.elastic.co/t/rejected-thread-pool/212395/2 "2019-12-19T07:43:14Z")
Hi @jdambly, this looks like an Elasticsearch question more than an ECK question. I suggest you ask it in [https://discuss.elastic.co/c/elasticsearch/6](https://discuss.elastic.co/c/elasticsearch/6) instead. ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [December 19, 2019, 8:56am UTC](https://discuss.elastic.co/t/rejected-thread-pool/212395/3 "2019-12-19T08:56:55Z")
The `write` threadpool is used to index documents, so it looks like this node cannot keep up with the indexing load. There's not a lot of information to go on here, but two common issues that can cause this are that the node is faulty (e.g. it has slow or failing disks) or is doing more than its fair share of work (e.g. it has more shards of "hot" indices than the other nodes). ---
**Author:** ![jdambly](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jdambly/32/44286_2.png) [@jdambly](https://discuss.elastic.co/u/jdambly)\ **Post date:** [December 19, 2019, 8:15pm UTC](https://discuss.elastic.co/t/rejected-thread-pool/212395/4 "2019-12-19T20:15:00Z")
ok sure, how do you decide what the thread pool should be in k8s? if create a resource pool of say 4 cpus, should I also set the ES config to match? ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [December 19, 2019, 8:22pm UTC](https://discuss.elastic.co/t/rejected-thread-pool/212395/5 "2019-12-19T20:22:37Z")
Elasticsearch will by default set the size of its threadpools appropriately, and it's unlikely that you need to change that. ---
**Author:** ![jdambly](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jdambly/32/44286_2.png) [@jdambly](https://discuss.elastic.co/u/jdambly)\ **Post date:** [December 20, 2019, 12:20am UTC](https://discuss.elastic.co/t/rejected-thread-pool/212395/6 "2019-12-20T00:20:01Z")
ok, so assuming the disk cannot keep up with all the writes, (I'm just writing logs) how can I quantify that? ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [December 20, 2019, 8:18am UTC](https://discuss.elastic.co/t/rejected-thread-pool/212395/7 "2019-12-20T08:18:29Z")
One way would be to would look at tools like `iostat` that report things from the OS's point of view, and compare this to your other better-performing nodes. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [January 17, 2020, 8:18am UTC](https://discuss.elastic.co/t/rejected-thread-pool/212395/8 "2020-01-17T08:18:35Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.