# Indies turn to red status and unable to connect after removing monitor-es-\*

**URL:** https://discuss.elastic.co/t/indies-turn-to-red-status-and-unable-to-connect-after-removing-monitor-es/235002
**Category:** Elasticsearch
**Created:** [May 30, 2020, 6:20am UTC](https://discuss.elastic.co/t/indies-turn-to-red-status-and-unable-to-connect-after-removing-monitor-es/235002 "2020-05-30T06:20:03Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![Huy\_Le1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/huy_le1/32/63101_2.png) [@Huy\_Le1](https://discuss.elastic.co/u/Huy_Le1)
#### Post date: [June 1, 2020, 6:23am UTC](https://discuss.elastic.co/t/indies-turn-to-red-status-and-unable-to-connect-after-removing-monitor-es/235002/5 "2020-06-01T06:23:53Z")

</div>

@Christian_Dahlqvist, I just figured out that my problem may not due to the .monitoring-es-\* index. It happened after I restart elasticsearch service. Most of shards is unassigned after I restarted elasticsearch and I think it caused my indices is not indexed too. I followed the directions of Mr. [andy\_zhou](https://discuss.elastic.co/u/zqc0512) in this post [Unassigned shards, crashed cluster recovery](https://discuss.elastic.co/t/unassigned-shards-crashed-cluster-recovery/113833/6) and reconfigure my cluster as follow

```auto
curl -XPUT 'XXX.XXX.XXX.XXX:9200/_cluster/settings?pretty 33' -H 'Content-Type: application/json' -d'
{
"persistent" : {
"cluster.routing.allocation.enable": "all",
"cluster.routing.rebalance.enable": "all"
},
"transient": {
"cluster.routing.allocation.enable": "all",
"cluster.routing.rebalance.enable": "all"
}
}
'

```

My cluster runs with one node with version information I shared above.  
Here is more logs:

---

_[View the full topic](https://discuss.elastic.co/t/indies-turn-to-red-status-and-unable-to-connect-after-removing-monitor-es/235002)._