# I Have a Recovered cluster but unassigned can some one help
**URL:** https://discuss.elastic.co/t/i-have-a-recovered-cluster-but-unassigned-can-some-one-help/94461
**Category:** Elasticsearch
**Created:** [July 25, 2017, 10:25am UTC](https://discuss.elastic.co/t/i-have-a-recovered-cluster-but-unassigned-can-some-one-help/94461 "2017-07-25T10:25:33Z")
**Posts on this page:** 13
**Page:** 1
### Author:  [@Danny\_Crossby](https://discuss.elastic.co/u/Danny_Crossby)
#### Post date: [July 25, 2017, 10:25am UTC](https://discuss.elastic.co/t/i-have-a-recovered-cluster-but-unassigned-can-some-one-help/94461/1 "2017-07-25T10:25:33Z")
99abc 4 r UNASSIGNED CLUSTER\_RECOVERED
99abc 2 r UNASSIGNED CLUSTER\_RECOVERED
99abc 1 r UNASSIGNED CLUSTER\_RECOVERED
99abc 3 r UNASSIGNED CLUSTER\_RECOVERED
99abc 0 r UNASSIGNED CLUSTER\_RECOVERED
---
### Author:  [@dadoonet](https://discuss.elastic.co/u/dadoonet)
#### Post date: [July 25, 2017, 10:37am UTC](https://discuss.elastic.co/t/i-have-a-recovered-cluster-but-unassigned-can-some-one-help/94461/2 "2017-07-25T10:37:02Z")
If it's a cloud instance, please read [https://discuss.elastic.co/t/now-live-new-elastic-cloud-standard-support/841611](https://discuss.elastic.co/t/now-live-new-elastic-cloud-standard-support/841611) for how to request support for Elastic Cloud 🙂
---
### Author:  [@Danny\_Crossby](https://discuss.elastic.co/u/Danny_Crossby)
#### Post date: [July 25, 2017, 10:46am UTC](https://discuss.elastic.co/t/i-have-a-recovered-cluster-but-unassigned-can-some-one-help/94461/3 "2017-07-25T10:46:30Z")
no its not cloud instance
---
### Author:  [@dadoonet](https://discuss.elastic.co/u/dadoonet)
#### Post date: [July 25, 2017, 11:33am UTC](https://discuss.elastic.co/t/i-have-a-recovered-cluster-but-unassigned-can-some-one-help/94461/4 "2017-07-25T11:33:51Z")
Can you give more details then about what and how this happened. What are the logs? Any pending tasks ?
---
### Author:  [@mruthyu](https://discuss.elastic.co/u/mruthyu)
#### Post date: [July 25, 2017, 11:48am UTC](https://discuss.elastic.co/t/i-have-a-recovered-cluster-but-unassigned-can-some-one-help/94461/5 "2017-07-25T11:48:34Z")
I ran into same issue. After cluster recovery due to the network connectivity issue, 20 shards from 2 indices are in UNASSIGNED state for the time series index. Now the cluster state is RED. Looking into the option of recovering those UNASSIGNED indices so that the cluster state can become GREEN. No pending tasks as such.
---
### Author:  [@Danny\_Crossby](https://discuss.elastic.co/u/Danny_Crossby)
#### Post date: [July 25, 2017, 1:17pm UTC](https://discuss.elastic.co/t/i-have-a-recovered-cluster-but-unassigned-can-some-one-help/94461/6 "2017-07-25T13:17:51Z")
if u can please help on this error
ES2.2.0
```
{
"error":{
"root_cause":[
{
"type":"illegal_argument_exception",
"reason":"[allocate] allocation of [99ats][0] on node {Silhouette}{XGIzwCotTNSoYDiTiJgw5Q}{127.0.0.1}{127.0.0.1:9300} is not allowed, reason: [YES(allocation disabling is ignored)][YES(no allocation awareness enabled)][YES(no active primary shard yet)][YES(total shard limit disabled: [index: -1, cluster: -1] <= 0)][YES(node passes include/exclude/require filters)][THROTTLE(too many shards currently recovering [4], limit: [2])][YES(allocation disabling is ignored)][YES(only a single data node is present)][NO(primary shard is not yet active)][NO(shard cannot be allocated on same node [XGIzwCotTNSoYDiTiJgw5Q] it already exists on)][YES(shard not primary or relocation disabled)]"
}
],
"type":"illegal_argument_exception",
"reason":"[allocate] allocation of [99ats][0] on node {Silhouette}{XGIzwCotTNSoYDiTiJgw5Q}{127.0.0.1}{127.0.0.1:9300} is not allowed, reason: [YES(allocation disabling is ignored)][YES(no allocation awareness enabled)][YES(no active primary shard yet)][YES(total shard limit disabled: [index: -1, cluster: -1] <= 0)][YES(node passes include/exclude/require filters)][THROTTLE(too many shards currently recovering [4], limit: [2])][YES(allocation disabling is ignored)][YES(only a single data node is present)][NO(primary shard is not yet active)][NO(shard cannot be allocated on same node [XGIzwCotTNSoYDiTiJgw5Q] it already exists on)][YES(shard not primary or relocation disabled)]"
},
"status":400
}
```
---
### Author:  [@dadoonet](https://discuss.elastic.co/u/dadoonet)
#### Post date: [July 25, 2017, 1:52pm UTC](https://discuss.elastic.co/t/i-have-a-recovered-cluster-but-unassigned-can-some-one-help/94461/7 "2017-07-25T13:52:22Z")
Please format your code. I edited your post to make that readable.
> too many shards currently recovering [4], limit: [2]
I believe you need to wait that the first 2 shards are finished recovering.
It's unclear to me what command you actually ran and the reason you are in this situation.
BTW you should upgrade to latest 2.x version.
---
### Author:  [@mruthyu](https://discuss.elastic.co/u/mruthyu)
#### Post date: [July 26, 2017, 6:47am UTC](https://discuss.elastic.co/t/i-have-a-recovered-cluster-but-unassigned-can-some-one-help/94461/8 "2017-07-26T06:47:37Z")
Let me know If I have to have a different post. Just don't wanted to interfere in this conversation. After the cluster recovery two time series indices were in UNASSIGNED state. Any idea why it happens during cluster recovery and how to recover the UNASSIGNED shards? Since the Primary is also in UNASSIGNED state, the cluster is RED. I don't want to delete those indices.
---
### Author:  [@mruthyu](https://discuss.elastic.co/u/mruthyu)
#### Post date: [July 26, 2017, 6:49am UTC](https://discuss.elastic.co/t/i-have-a-recovered-cluster-but-unassigned-can-some-one-help/94461/9 "2017-07-26T06:49:38Z")
The elasticsearch version is 5.4.3.
---
### Author:  [@Danny\_Crossby](https://discuss.elastic.co/u/Danny_Crossby)
#### Post date: [July 26, 2017, 7:01am UTC](https://discuss.elastic.co/t/i-have-a-recovered-cluster-but-unassigned-can-some-one-help/94461/10 "2017-07-26T07:01:38Z")
```auto
$ curl -XGET localhost:9200/_cat/shards?h=index,shard,prirep,state,unassigned.reason| grep UNASSIGNED
99ats 3 r UNASSIGNED CLUSTER_RECOVERED
99ats 1 r UNASSIGNED CLUSTER_RECOVERED
99ats 4 r UNASSIGNED CLUSTER_RECOVERED
99ats 2 p UNASSIGNED ALLOCATION_FAILED
99ats 2 r UNASSIGNED CLUSTER_RECOVERED
99ats 0 r UNASSIGNED CLUSTER_RECOVERED
```
---
### Author:  [@dadoonet](https://discuss.elastic.co/u/dadoonet)
#### Post date: [July 27, 2017, 4:06pm UTC](https://discuss.elastic.co/t/i-have-a-recovered-cluster-but-unassigned-can-some-one-help/94461/11 "2017-07-27T16:06:33Z")
Yes open another thread as it will be confusing otherwise.
---
### Author:  [@dadoonet](https://discuss.elastic.co/u/dadoonet)
#### Post date: [July 27, 2017, 4:07pm UTC](https://discuss.elastic.co/t/i-have-a-recovered-cluster-but-unassigned-can-some-one-help/94461/12 "2017-07-27T16:07:20Z")
What is the status on this now?
> 99ats 2 p UNASSIGNED ALLOCATION\_FAILED
I believe you should see things in logs.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [August 24, 2017, 4:07pm UTC](https://discuss.elastic.co/t/i-have-a-recovered-cluster-but-unassigned-can-some-one-help/94461/13 "2017-08-24T16:07:34Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.