# X of y shards failed

**URL:** <https://discuss.elastic.co/t/x-of-y-shards-failed/285559>\
**Category:** Kibana\
**Created:** [September 30, 2021, 8:55am UTC](https://discuss.elastic.co/t/x-of-y-shards-failed/285559 "2021-09-30T08:55:31Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Noursh](https://avatars.discourse-cdn.com/v4/letter/n/bc8723/32.png) [@Noursh](https://discuss.elastic.co/u/Noursh)\
**Post date:** [September 30, 2021, 8:55am UTC](https://discuss.elastic.co/t/x-of-y-shards-failed/285559/1 "2021-09-30T08:55:31Z")

</div>

Type: es\_rejected\_execution\_exception

Reason: rejected execution of org.Elasticsearch.common.util.concurrent.TimedRunnable@5ec3e8 on QueueResizingEsThreadPoolExecutor

I had monitored the CPU and RAM and all the metrics is ok.  
also tried to reroute the shard to another node.

still get the same error -  
ES and Kibana - V 7.13.2

---

<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:** [September 30, 2021, 10:48pm UTC](https://discuss.elastic.co/t/x-of-y-shards-failed/285559/2 "2021-09-30T22:48:22Z")

</div>

Can you share more of this error please.

What is the output from the `_cluster/stats?pretty&human` API?

---

<div class="post-metadata">

**Author:** ![Noursh](https://avatars.discourse-cdn.com/v4/letter/n/bc8723/32.png) [@Noursh](https://discuss.elastic.co/u/Noursh)\
**Post date:** [October 12, 2021, 1:23pm UTC](https://discuss.elastic.co/t/x-of-y-shards-failed/285559/4 "2021-10-12T13:23:36Z")

</div>

any updates ?  
what could be the problem?  
what do I have to check ?

---

<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 12, 2021, 9:26pm UTC](https://discuss.elastic.co/t/x-of-y-shards-failed/285559/5 "2021-10-12T21:26:31Z")

</div>

Are you using Monitoring for your cluster? It looks like you are getting overloads on your node(s) and filling threadpools.

How are you indexing data into Elasticsearch?  
What do your Elasticsearch logs show?

---

<div class="post-metadata">

**Author:** ![Noursh](https://avatars.discourse-cdn.com/v4/letter/n/bc8723/32.png) [@Noursh](https://discuss.elastic.co/u/Noursh)\
**Post date:** [October 14, 2021, 7:45am UTC](https://discuss.elastic.co/t/x-of-y-shards-failed/285559/6 "2021-10-14T07:45:45Z")

</div>

yes I have a monitoring process,  
indexing - using Logstash  
Logs - looks ok nothing relevant I think.

---

<div class="post-metadata">

**Author:** ![Noursh](https://avatars.discourse-cdn.com/v4/letter/n/bc8723/32.png) [@Noursh](https://discuss.elastic.co/u/Noursh)\
**Post date:** [November 7, 2021, 1:51pm UTC](https://discuss.elastic.co/t/x-of-y-shards-failed/285559/7 "2021-11-07T13:51:22Z")

</div>

any updates ?

---

<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:** [November 7, 2021, 11:55pm UTC](https://discuss.elastic.co/t/x-of-y-shards-failed/285559/8 "2021-11-07T23:55:45Z")

</div>

Unfortunately we need more information here.

We need to see the complete error you are getting.  
We'd need to see your Elasticsearch logs from around the time of this error as well.

---

<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:** [December 5, 2021, 11:55pm UTC](https://discuss.elastic.co/t/x-of-y-shards-failed/285559/9 "2021-12-05T23:55:50Z")

</div>

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