# Shards not allocating after rolling upgrade

**URL:** <https://discuss.elastic.co/t/shards-not-allocating-after-rolling-upgrade/155573>\
**Category:** Elasticsearch\
**Created:** [November 6, 2018, 3:45pm UTC](https://discuss.elastic.co/t/shards-not-allocating-after-rolling-upgrade/155573 "2018-11-06T15:45:11Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![juiip](https://avatars.discourse-cdn.com/v4/letter/j/bc8723/32.png) [@juiip](https://discuss.elastic.co/u/juiip)\
**Post date:** [November 6, 2018, 3:45pm UTC](https://discuss.elastic.co/t/shards-not-allocating-after-rolling-upgrade/155573/1 "2018-11-06T15:45:11Z")

</div>

I have a 2 node cluster on Elasticsearch 5.6.12

I followed this upgrade guide: [https://www.elastic.co/guide/en/elasticsearch/reference/5.6/rolling-upgrades.html](https://www.elastic.co/guide/en/elasticsearch/reference/5.6/rolling-upgrades.html)

After running:

```
PUT _cluster/settings
{
  "transient": {
    "cluster.routing.allocation.enable": "all"
  }
}

```

`GET _cat/health` is still returning yellow cluster status and shards remain unallocated?

---

<div class="post-metadata">

**Author:** ![juiip](https://avatars.discourse-cdn.com/v4/letter/j/bc8723/32.png) [@juiip](https://discuss.elastic.co/u/juiip)\
**Post date:** [November 6, 2018, 5:39pm UTC](https://discuss.elastic.co/t/shards-not-allocating-after-rolling-upgrade/155573/2 "2018-11-06T17:39:52Z")

</div>

Never mind - it was a high disk watermark [90%] exceeded warning

---

<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:** [December 4, 2018, 5:52pm UTC](https://discuss.elastic.co/t/shards-not-allocating-after-rolling-upgrade/155573/3 "2018-12-04T17:52:55Z")

</div>

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