# Elasticsearch NoShardAvailableActionException

**URL:** <https://discuss.elastic.co/t/elasticsearch-noshardavailableactionexception/328279>\
**Category:** Elasticsearch\
**Created:** [March 22, 2023, 5:22pm UTC](https://discuss.elastic.co/t/elasticsearch-noshardavailableactionexception/328279 "2023-03-22T17:22:09Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Lohanna\_Sarah](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lohanna_sarah/32/116106_2.png) [@Lohanna\_Sarah](https://discuss.elastic.co/u/Lohanna_Sarah)\
**Post date:** [March 22, 2023, 5:22pm UTC](https://discuss.elastic.co/t/elasticsearch-noshardavailableactionexception/328279/1 "2023-03-22T17:22:09Z")

</div>

Suppose a cluster is composed of three data nodes. If one of the nodes throws the exception "NoShardAvailableActionException", what is the impact on the cluster and how is the request handled? Specifically, is the request automatically routed to one of the other two nodes, and if so, how does this process work?

---

<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:** [March 22, 2023, 8:49pm UTC](https://discuss.elastic.co/t/elasticsearch-noshardavailableactionexception/328279/2 "2023-03-22T20:49:46Z")

</div>

Is this a theoretical question or are you trying to resolve an issue?

---

<div class="post-metadata">

**Author:** ![Lohanna\_Sarah](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lohanna_sarah/32/116106_2.png) [@Lohanna\_Sarah](https://discuss.elastic.co/u/Lohanna_Sarah)\
**Post date:** [March 22, 2023, 9:12pm UTC](https://discuss.elastic.co/t/elasticsearch-noshardavailableactionexception/328279/3 "2023-03-22T21:12:48Z")

</div>

Both

---

<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:** [March 22, 2023, 9:29pm UTC](https://discuss.elastic.co/t/elasticsearch-noshardavailableactionexception/328279/4 "2023-03-22T21:29:37Z")

</div>

It'd be useful if you could share more about the problem please.

That sort of error can come from a few things, so we're just guessing as to what might be causing it here.

---

<div class="post-metadata">

**Author:** ![Lohanna\_Sarah](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lohanna_sarah/32/116106_2.png) [@Lohanna\_Sarah](https://discuss.elastic.co/u/Lohanna_Sarah)\
**Post date:** [March 23, 2023, 1:35pm UTC](https://discuss.elastic.co/t/elasticsearch-noshardavailableactionexception/328279/5 "2023-03-23T13:35:51Z")

</div>

> [@warkolm](#):
>
> That sort of error can come from a few things, so we're just guessing as to what might be causing it here.

I am running an Elasticsearch cluster inside a Kubernetes cluster (ks8). Occasionally, the Elasticsearch data node needs to be restarted, which results in some shards requiring initialization. I have observed that sometimes all shards of an index may have this status. I suspect that this is the reason why the NoShardAvailableActionException is occurring.

---

<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:** [April 20, 2023, 1:35pm UTC](https://discuss.elastic.co/t/elasticsearch-noshardavailableactionexception/328279/6 "2023-04-20T13:35:59Z")

</div>

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