# UNASSIGNED NODE\_LEFT
**URL:** https://discuss.elastic.co/t/unassigned-node-left/343737
**Category:** Elasticsearch
**Created:** [September 25, 2023, 9:51am UTC](https://discuss.elastic.co/t/unassigned-node-left/343737 "2023-09-25T09:51:30Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@PugachevLB](https://discuss.elastic.co/u/PugachevLB)
#### Post date: [September 25, 2023, 9:51am UTC](https://discuss.elastic.co/t/unassigned-node-left/343737/1 "2023-09-25T09:51:30Z")
We have a cluster of 30 nodes (3 phys servers 64 cpu + 512 mem with 10 ES instances on each (1 master + 9 data)).
Sometimes after uploading a new index (~700 Gb 24 shards \* 2 rep factor) we have some instances crushed (3-4). And we must to start them manually. After that index has some replica shards in UNASSIGNED state NODE\_LEFT with "allocate\_explanation" : "Elasticsearch is retrieving information about this shard from one or more nodes. It will make an allocation decision after it receives this information. Please wait.".
How can i understand "what info and from who cluster is waiting"?
Api method `POST _cluster/reroute?retry_failed=true` didnt help us.
PS: we have enabled routing awarness
in masters config:
```auto
cluster.routing.allocation.awareness.attributes: rack_id
```
in data node config:
```auto
node.attr.rack_id:
```
Persistent cluster settings (force awareness + same\_shard):
```auto
{
"persistent": {
"cluster": {
"routing": {
"allocation": {
"awareness": {
"force": {
"rack_id": {
"values": "srv1_name,srv2_name,srv3_name"
}
}
},
"same_shard": {
"host": "true"
}
}
}
}
},
"transient": {}
}
```
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [October 23, 2023, 9:52am UTC](https://discuss.elastic.co/t/unassigned-node-left/343737/2 "2023-10-23T09:52:11Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.