# Unassigned shards: NODE\_LEFT (Cloud)
**URL:** https://discuss.elastic.co/t/unassigned-shards-node-left-cloud/260444
**Category:** Elasticsearch
**Created:** [January 7, 2021, 1:30pm UTC](https://discuss.elastic.co/t/unassigned-shards-node-left-cloud/260444 "2021-01-07T13:30:08Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@bogdan\_copocean](https://discuss.elastic.co/u/bogdan_copocean)
#### Post date: [January 7, 2021, 1:30pm UTC](https://discuss.elastic.co/t/unassigned-shards-node-left-cloud/260444/1 "2021-01-07T13:30:08Z")
Hello guys,
I encountered a few problems with my Elasticsearch cluster (on cloud) and exactly, i have around 25 unassigned shards with the reason NODE\_LEFT and one with REPLICA\_ADDED (after I tried to add a replica).
I want to solve this problem without having to delete the indices and I looked around for a solution, but I didn't see one for the cloud.
Any suggestions?
Thanks!
---
### Author:  [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)
#### Post date: [January 7, 2021, 1:45pm UTC](https://discuss.elastic.co/t/unassigned-shards-node-left-cloud/260444/2 "2021-01-07T13:45:14Z")
`NODE_LEFT` just says that the shard became unassigned because a node left the cluster. The more interesting question is why the shard is not being assigned again, and for that you should use the [cluster allocation explain API](https://www.elastic.co/guide/en/elasticsearch/reference/current/cluster-allocation-explain.html).
---
### Author:  [@bogdan\_copocean](https://discuss.elastic.co/u/bogdan_copocean)
#### Post date: [January 11, 2021, 7:29am UTC](https://discuss.elastic.co/t/unassigned-shards-node-left-cloud/260444/3 "2021-01-11T07:29:21Z")
Hi David and thank you for replying. This is the output from the cluster allocation explain API:
{
"decider" : "same\_shard",
"decision" : "NO",
"explanation" : "a copy of this shard is already allocated to this node [[test\_index-000002][0], node[6NlWny21g5SdCMUzGtlcgWaszSQ], [P], s[STARTED], a[id=\_AZRb0yaTJWOncpxzpNB0dsy8Q]]"
},
{
"decider" : "awareness",
"decision" : "NO",
"explanation" : "there are too many copies of the shard allocated to nodes with attribute [logical\_availability\_zone], there are [2] total configured shard copies for this shard id and [2] total attribute values, expected the allocated shard count per attribute [2] to be less than or equal to the upper bound of the required number of shards per attribute [1]"
}
It is pretty intuitive why this happened, but I don't know how to solve it.
---
### Author:  [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)
#### Post date: [January 11, 2021, 7:47am UTC](https://discuss.elastic.co/t/unassigned-shards-node-left-cloud/260444/4 "2021-01-11T07:47:10Z")
That's not the full output. That's just saying we can't allocate a copy of `[test_index-000002][0]` to this node because there's already a copy there.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [February 8, 2021, 7:47am UTC](https://discuss.elastic.co/t/unassigned-shards-node-left-cloud/260444/5 "2021-02-08T07:47:16Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.