# Search\_phase\_execution\_exception error: rejected execution of org.elasticsearch.common.util.concurrent.TimedRunnable@ on QueueResizingEsThreadPoolExecutor

**URL:** <https://discuss.elastic.co/t/search-phase-execution-exception-error-rejected-execution-of-org-elasticsearch-common-util-concurrent-timedrunnable-on-queueresizingesthreadpoolexecutor/294008>\
**Category:** Elasticsearch\
**Created:** [January 11, 2022, 9:54am UTC](https://discuss.elastic.co/t/search-phase-execution-exception-error-rejected-execution-of-org-elasticsearch-common-util-concurrent-timedrunnable-on-queueresizingesthreadpoolexecutor/294008 "2022-01-11T09:54:16Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![bugb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bugb/32/90933_2.png) [@bugb](https://discuss.elastic.co/u/bugb)\
**Post date:** [January 11, 2022, 9:54am UTC](https://discuss.elastic.co/t/search-phase-execution-exception-error-rejected-execution-of-org-elasticsearch-common-util-concurrent-timedrunnable-on-queueresizingesthreadpoolexecutor/294008/1 "2022-01-11T09:54:16Z")

</div>

Sometimes I got this error from my client node, is there any ideas to fix this?

`search_phase_execution_exception: \n at onBody (/var/server/app/node_modules/es7/lib/Transport.js:367:23)\n at IncomingMessage.onEnd (/var/server/app/node_modules/es7/lib/Transport.js:291:11)\n at IncomingMessage.emit (events.js:327:22)\n at IncomingMessage.EventEmitter.emit (domain.js:482:12)\n at endReadableNT (_stream_readable.js:1221:12)\n at processTicksAndRejections (internal/process/task_queues.js:84:21) || {\"error\":{\"root_cause\":[],\"type\":\"search_phase_execution_exception\",\"reason\":\"\",\"phase\":\"fetch\",\"grouped\":true,\"failed_shards\":[],\"caused_by\":{\"type\":\"es_rejected_execution_exception\",\"reason\":\"rejected execution of org.elasticsearch.common.util.concurrent.TimedRunnable@6e1d4b05 on QueueResizingEsThreadPoolExecutor[name = my-client-node/search, queue capacity = 1000, min queue capacity = 1000, max queue capacity = 1000, frame size = 2000, targeted response rate = 1s, task execution EWMA = 95.4ms, adjustment amount = 50, org.elasticsearch.common.util.concurrent.QueueResizingEsThreadPoolExecutor@4686a537[Running, pool size = 4, active threads = 4, queued tasks = 1000, completed tasks = 5426155755]]\"}},\"status\":429}","time":"2022-01-11T09:16:49.770Z"`

Should I add more data nodes / client nodes or increase the queue size?

---

<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:** [January 11, 2022, 10:31pm UTC](https://discuss.elastic.co/t/search-phase-execution-exception-error-rejected-execution-of-org-elasticsearch-common-util-concurrent-timedrunnable-on-queueresizingesthreadpoolexecutor/294008/2 "2022-01-11T22:31:53Z")

</div>

TLDR you are overloading your Elasticsearch node(s).  
You'd need to dig into Monitoring information to discover why.

---

<div class="post-metadata">

**Author:** ![bugb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bugb/32/90933_2.png) [@bugb](https://discuss.elastic.co/u/bugb)\
**Post date:** [January 12, 2022, 8:18am UTC](https://discuss.elastic.co/t/search-phase-execution-exception-error-rejected-execution-of-org-elasticsearch-common-util-concurrent-timedrunnable-on-queueresizingesthreadpoolexecutor/294008/3 "2022-01-12T08:18:08Z")

</div>

What the information that I should collect? RAM, CPU, ...?

---

<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:** [February 9, 2022, 8:18am UTC](https://discuss.elastic.co/t/search-phase-execution-exception-error-rejected-execution-of-org-elasticsearch-common-util-concurrent-timedrunnable-on-queueresizingesthreadpoolexecutor/294008/4 "2022-02-09T08:18:54Z")

</div>

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