# Unassigned shards on elasticloud system indexes with 0 replica settings
**URL:** https://discuss.elastic.co/t/unassigned-shards-on-elasticloud-system-indexes-with-0-replica-settings/221612
**Category:** Elasticsearch
**Created:** [March 2, 2020, 4:02am UTC](https://discuss.elastic.co/t/unassigned-shards-on-elasticloud-system-indexes-with-0-replica-settings/221612 "2020-03-02T04:02:15Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@MagicNotElastic](https://discuss.elastic.co/u/MagicNotElastic)
#### Post date: [March 2, 2020, 4:02am UTC](https://discuss.elastic.co/t/unassigned-shards-on-elasticloud-system-indexes-with-0-replica-settings/221612/1 "2020-03-02T04:02:15Z")
Using 1 node with number\_of\_replicas": "0", all beats indexes working properly, except system:
.monitoring-kibana
.watcher-history
.watches
It seem, that all system indexes have unassigned replicas, but all my settings seems correct.
As a side note, I created 2 zone environment, which I've shrinked to 1 zone.
_POST \_cluster/reroute?pretty_
didn't help
Example of index template for **.monitoring-kibana** :
```
{
"index": {
"format": "7",
"codec": "best_compression",
"number_of_shards": "1",
"auto_expand_replicas": "0-1",
"number_of_replicas": "0"
}
}
```
Yet all indexes are created with 1 replica
Other settings:
cluster.routing.rebalance.enable" : "all"
---
### Author:  [@MagicNotElastic](https://discuss.elastic.co/u/MagicNotElastic)
#### Post date: [March 2, 2020, 4:20am UTC](https://discuss.elastic.co/t/unassigned-shards-on-elasticloud-system-indexes-with-0-replica-settings/221612/2 "2020-03-02T04:20:15Z")
setting auto\_expand\_replicas to false will turn index green. What I don't understand is why this setting is not automatically adjusted for system indexes in managed cloud service?
---
### Author:  [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)
#### Post date: [March 2, 2020, 5:34am UTC](https://discuss.elastic.co/t/unassigned-shards-on-elasticloud-system-indexes-with-0-replica-settings/221612/3 "2020-03-02T05:34:39Z")
How many shards do you have on the node? How much disk space have you got left?
---
### Author:  [@MagicNotElastic](https://discuss.elastic.co/u/MagicNotElastic)
#### Post date: [March 2, 2020, 7:22am UTC](https://discuss.elastic.co/t/unassigned-shards-on-elasticloud-system-indexes-with-0-replica-settings/221612/4 "2020-03-02T07:22:26Z")
74 shards, one per index + 20 yellow system ones.
plenty of space, 5-10% taken up on 2 nodes warm-hot.
---
### Author:  [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)
#### Post date: [March 2, 2020, 7:58am UTC](https://discuss.elastic.co/t/unassigned-shards-on-elasticloud-system-indexes-with-0-replica-settings/221612/5 "2020-03-02T07:58:10Z")
Yellow status is not a problem as it just means that you have a replica shard configured which can not be allocated as you now only have one node.
---
### Author:  [@MagicNotElastic](https://discuss.elastic.co/u/MagicNotElastic)
#### Post date: [March 2, 2020, 10:07am UTC](https://discuss.elastic.co/t/unassigned-shards-on-elasticloud-system-indexes-with-0-replica-settings/221612/6 "2020-03-02T10:07:39Z")
I understand thank you, but I like things tidy, let's imagine a scenario where I have to prove the state of cluster is green and healthy.
If auto\_expand\_replicas defaults to false according to the documentation, then it seems it's an issue created by downsizing cluster from 2 zones to 1. If that's the case I guess it should be considered a bug and added to the elasticloud automation process.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [March 30, 2020, 10:07am UTC](https://discuss.elastic.co/t/unassigned-shards-on-elasticloud-system-indexes-with-0-replica-settings/221612/7 "2020-03-30T10:07:40Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.