# Yellow heath, Unassigned shards after restart
**URL:** https://discuss.elastic.co/t/yellow-heath-unassigned-shards-after-restart/249775
**Category:** Elasticsearch
**Created:** [September 24, 2020, 8:48am UTC](https://discuss.elastic.co/t/yellow-heath-unassigned-shards-after-restart/249775 "2020-09-24T08:48:03Z")
**Posts on this page:** 8
**Page:** 1
### Author:  [@Graham\_Smart](https://discuss.elastic.co/u/Graham_Smart)
#### Post date: [September 24, 2020, 8:48am UTC](https://discuss.elastic.co/t/yellow-heath-unassigned-shards-after-restart/249775/1 "2020-09-24T08:48:03Z")
Hi Guys, Im sure this is a simple one, but i cant seem to resolve.
My ES node ran our of JVM space. So i modified its upper limit and restarted ES as ive done many times.
This time round, it refuses to go Green. Its been yellow now for two days.
The ONLY thing i can find is two shards not being assigned. Logs are empty of anything relevant.
Any thoughts?
Thanks in advance!
```
{
"cluster_name" : "elasticsearch",
"status" : "yellow",
"timed_out" : false,
"number_of_nodes" : 1,
"number_of_data_nodes" : 1,
"active_primary_shards" : 611,
"active_shards" : 611,
"relocating_shards" : 0,
"initializing_shards" : 0,
"unassigned_shards" : 4,
"delayed_unassigned_shards" : 0,
"number_of_pending_tasks" : 0,
"number_of_in_flight_fetch" : 0,
"task_max_waiting_in_queue_millis" : 0,
"active_shards_percent_as_number" : 99.34959349593497
}
```
---
### Author:  [@Graham\_Smart](https://discuss.elastic.co/u/Graham_Smart)
#### Post date: [September 24, 2020, 8:59am UTC](https://discuss.elastic.co/t/yellow-heath-unassigned-shards-after-restart/249775/2 "2020-09-24T08:59:31Z")
```
{
* "state": "UNASSIGNED",
* "primary": false,
* "node": null,
* "relocating_node": null,
* "shard": 0,
* "index": "metrics-index_pattern_placeholder",
* "recovery_source": {
* "type": "PEER"},
* "unassigned_info": {
* "reason": "CLUSTER_RECOVERED",
* "at": "2020-09-22T08:19:35.187Z",
* "delayed": false,
* "allocation_status": "no_attempt"}
}
```
---
### Author:  [@Graham\_Smart](https://discuss.elastic.co/u/Graham_Smart)
#### Post date: [September 24, 2020, 9:04am UTC](https://discuss.elastic.co/t/yellow-heath-unassigned-shards-after-restart/249775/3 "2020-09-24T09:04:48Z")
More info
```
{
* "index": "logs-index_pattern_placeholder",
* "shard": 0,
* "primary": false,
* "current_state": "unassigned",
* "unassigned_info": {
* "reason": "CLUSTER_RECOVERED",
* "at": "2020-09-22T08:19:35.187Z",
* "last_allocation_status": "no_attempt"},
* "can_allocate": "no",
* "allocate_explanation": "cannot allocate because allocation is not permitted to any of the nodes",
* "node_allocation_decisions": [
* {
* "node_id": "WMC9UvMnTlWXGZGIjHuJqA",
* "node_name": "siem-es-01",
* "transport_address": "127.0.0.1:9300",
* "node_attributes": {
* "ml.machine_memory": "8348577792",
* "xpack.installed": "true",
* "transform.node": "true",
* "ml.max_open_jobs": "20"},
* "node_decision": "no",
* "deciders": [
* {
* "decider": "same_shard",
* "decision": "NO",
* "explanation": "a copy of this shard is already allocated to this node [[logs-index_pattern_placeholder][0], node[WMC9UvMnTlWXGZGIjHuJqA], [P], s[STARTED], a[id=0rZvrNBASBadFXKGJQOOdw]]"}]}]
}
```
---
### Author:  [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)
#### Post date: [September 24, 2020, 9:05am UTC](https://discuss.elastic.co/t/yellow-heath-unassigned-shards-after-restart/249775/4 "2020-09-24T09:05:32Z")
Do the indices with unassigned shard by any chance have a replica shard configured?
---
### Author:  [@Graham\_Smart](https://discuss.elastic.co/u/Graham_Smart)
#### Post date: [September 24, 2020, 9:08am UTC](https://discuss.elastic.co/t/yellow-heath-unassigned-shards-after-restart/249775/5 "2020-09-24T09:08:46Z")
Still new to it.. where would i check that?
It does appear that one shard is allocated and fine, but there is another that isnt.. so that does sound and make sense..
---
### Author:  [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)
#### Post date: [September 24, 2020, 9:12am UTC](https://discuss.elastic.co/t/yellow-heath-unassigned-shards-after-restart/249775/6 "2020-09-24T09:12:20Z")
Check the index settings. As you have only one node, replica shards will never get allocated as Elasticsearch never allocates them on the same node as the primary.
---
### Author:  [@Graham\_Smart](https://discuss.elastic.co/u/Graham_Smart)
#### Post date: [September 24, 2020, 9:22am UTC](https://discuss.elastic.co/t/yellow-heath-unassigned-shards-after-restart/249775/7 "2020-09-24T09:22:13Z")
Thanks,
Seems to fix the issue updating the index setting to 0 replicas..
No idea why it randomly decided to add an index with 1 replica on a single node cluster.
Cheers again
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [October 22, 2020, 9:22am UTC](https://discuss.elastic.co/t/yellow-heath-unassigned-shards-after-restart/249775/8 "2020-10-22T09:22:22Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.