# Unassigned shard reason unclear
**URL:** https://discuss.elastic.co/t/unassigned-shard-reason-unclear/228478
**Category:** Elasticsearch
**Created:** [April 17, 2020, 8:53am UTC](https://discuss.elastic.co/t/unassigned-shard-reason-unclear/228478 "2020-04-17T08:53:27Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@ntsh999](https://discuss.elastic.co/u/ntsh999)
#### Post date: [April 17, 2020, 8:53am UTC](https://discuss.elastic.co/t/unassigned-shard-reason-unclear/228478/1 "2020-04-17T08:53:27Z")
My ElasticSearch Cluster is in RED status, when I used the GET \_cluster/allocation/explain?pretty API call I got the following output. I can see that there are 2 unassigned shards , but the allocate\_explanation and can\_allocate mentioned in the API output does not make any sense to me. Can some help me in understanding what should be the fix for this unassigned shards reason ?
```auto
{
"index" : "filebeat-7.2.0-2020.04.12",
"shard" : 0,
"primary" : true,
"current_state" : "unassigned",
"unassigned_info" : {
"reason" : "INDEX_CREATED",
"at" : "2020-04-17T01:00:17.446Z",
"last_allocation_status" : "no"
},
"can_allocate" : "yes",
"allocate_explanation" : "can allocate the shard",
"target_node" : {
"id" : "9W8u53F0QhSkSKjzrtNytQ",
"name" : "elasticsearch-data-0",
"transport_address" : "10.244.0.218:9300"
},
"node_allocation_decisions" : [
{
"node_id" : "9W8u53F0QhSkSKjzrtNytQ",
"node_name" : "elasticsearch-data-0",
"transport_address" : "10.244.0.218:9300",
"node_decision" : "yes",
"weight_ranking" : 1
},
{
"node_id" : "pOyKt1QGTiycRHHhFo96fw",
"node_name" : "elasticsearch-data-1",
"transport_address" : "10.244.2.150:9300",
"node_decision" : "yes",
"weight_ranking" : 2
}
]
}
```
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [May 15, 2020, 8:53am UTC](https://discuss.elastic.co/t/unassigned-shard-reason-unclear/228478/2 "2020-05-15T08:53:35Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.