# Cluster Red after system patching forced upgrade 7.16.1 -\> 7.17.1

**URL:** <https://discuss.elastic.co/t/cluster-red-after-system-patching-forced-upgrade-7-16-1-7-17-1/300592>\
**Category:** Elasticsearch\
**Created:** [March 24, 2022, 3:12pm UTC](https://discuss.elastic.co/t/cluster-red-after-system-patching-forced-upgrade-7-16-1-7-17-1/300592 "2022-03-24T15:12:10Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![thealy](https://avatars.discourse-cdn.com/v4/letter/t/41988e/32.png) [@thealy](https://discuss.elastic.co/u/thealy)\
**Post date:** [March 24, 2022, 3:12pm UTC](https://discuss.elastic.co/t/cluster-red-after-system-patching-forced-upgrade-7-16-1-7-17-1/300592/1 "2022-03-24T15:12:10Z")

</div>

We have and 8 node cluster where the nodes are all running Centos 7. When they were rebooted for patching, the ES version went to 7.17.1. The master node is periodically scrolling these errors:

```auto
[2022-03-24T10:59:50,530][WARN][o.e.x.m.MonitoringService] [es02] monitoring execution failed
org.elasticsearch.xpack.monitoring.exporter.ExportException: failed to flush export bulks
.....
Caused by: org.elasticsearch.xpack.monitoring.exporter.ExportException: bulk [default_local] reports failures when exporting documents
  at org.elasticsearch.xpack.monitoring.exporter.local.LocalBulk.throwExportException(LocalBulk.java:131) ~[?:?]
  ... 23 more

```

Kibana will not start so I'm kind of blind. ES-head plugin shows cluster health: red (1538 of 3101), and the 1538 is not increasing.

I have attempted to re-enable routing with:

```auto
curl -H 'Content-Type: application/json' -XPUT 'xx.yy.zz:9200/_cluster/settings' -d '{ 
"transient": 
    { "cluster.routing.allocation.enable" : "all" 
    }
}'

```

and

```auto
curl -H 'Content-Type: application/json' -XPUT 'xx.yy.zz:9200/_cluster/settings' -d '{ 
"transient": 
    { "cluster.routing.rebalance.enable" : "all" 
    }
}'

```

both of which are acknowledged. I also tried:

```auto
curl --noproxy '*' -X PUT "xxx.yyy.zzz:9200/_cluster/settings?pretty" -H 'Content-Type: application/json' -d'
{
  "persistent": {
    "cluster.routing.allocation.enable": "all"
  }
}'

```

which also is acknowledged but seems to make no difference.

The index referred to in the error - UnavailableShardsException[[.monitoring-es-7-2022.03.24][0] primary shard is not active - shows as one un-allocated shard.

I would be very grateful for any suggestions to get shards moving again and get out of the Red status.

---

<div class="post-metadata">

**Author:** ![thealy](https://avatars.discourse-cdn.com/v4/letter/t/41988e/32.png) [@thealy](https://discuss.elastic.co/u/thealy)\
**Post date:** [March 24, 2022, 7:00pm UTC](https://discuss.elastic.co/t/cluster-red-after-system-patching-forced-upgrade-7-16-1-7-17-1/300592/2 "2022-03-24T19:00:59Z")

</div>

In case anyone faces a similar situation, the problem was due to apparently improperly formatted "cluster.routing.allocation.include.\_host" host names, which were not fully qualified domain names. I cleared the filter using this:

```auto
curl -H 'Content-Type: application/json' -XPUT 'xxx.yyy.zzz:9200/_cluster/settings' -d '
{
  "transient" : {
    "cluster.routing.allocation.include._host" : null
  }
}'

```

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [April 21, 2022, 7:01pm UTC](https://discuss.elastic.co/t/cluster-red-after-system-patching-forced-upgrade-7-16-1-7-17-1/300592/3 "2022-04-21T19:01:49Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.