# Rolling restarts issue

**URL:** <https://discuss.elastic.co/t/rolling-restarts-issue/56118>\
**Category:** Elasticsearch\
**Created:** [July 21, 2016, 4:33pm UTC](https://discuss.elastic.co/t/rolling-restarts-issue/56118 "2016-07-21T16:33:07Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Michael1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/michael1/32/29279_2.png) [@Michael1](https://discuss.elastic.co/u/Michael1)\
**Post date:** [July 21, 2016, 4:33pm UTC](https://discuss.elastic.co/t/rolling-restarts-issue/56118/1 "2016-07-21T16:33:07Z")

</div>

Hello,

I made a change in elasticsearch.yml (disabling Shield for testing). First, I executed the following PUT on one of the master nodes directly ::

```auto
{
    "transient" : {
        "cluster.routing.allocation.enable" : "none"
    }
}

```

I then rebooted the node, but now I am stuck and do not know if the master node has joined the cluster already...there are 3 master nodes total.

I tried changing 'none' to 'all' and running it against that node but now I am getting nothing but 'master\_not\_discovered\_exception' 's in the response to the PUT request. The cluster seems to be down at this point.

Not sure what to do now...

---

<div class="post-metadata">

**Author:** ![jpcarey](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jpcarey/32/46668_2.png) [@jpcarey](https://discuss.elastic.co/u/jpcarey)\
**Post date:** [July 21, 2016, 4:41pm UTC](https://discuss.elastic.co/t/rolling-restarts-issue/56118/2 "2016-07-21T16:41:17Z")

</div>

On one of the master nodes that was not restarted, curl `_cat/master` or `_cat/nodes`. I would also take a look at the log file on the node that you restarted, and see why it was not able to join the cluster.

You should not enable allocation on a rolling upgrade until the node has rejoined the cluster, it will cause the shards to be redistributed evenly amongst the current nodes in the cluster.

[https://www.elastic.co/guide/en/elasticsearch/reference/current/cat.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/cat.html)

---

<div class="post-metadata">

**Author:** ![Michael1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/michael1/32/29279_2.png) [@Michael1](https://discuss.elastic.co/u/Michael1)\
**Post date:** [July 21, 2016, 4:48pm UTC](https://discuss.elastic.co/t/rolling-restarts-issue/56118/3 "2016-07-21T16:48:44Z")

</div>

Well, I said whatever and just rebooted all of the master and data nodes at the same time, now it is back. Thankfully, this was not a production environment, but if it was, this would be a problem.

I followed the instructions for rolling restarts as it said, and this is a very basic cluster, so it is relatively unacceptable to me that nothing is mentioned about looking out for things like this.

---

<div class="post-metadata">

**Author:** ![Michael1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/michael1/32/29279_2.png) [@Michael1](https://discuss.elastic.co/u/Michael1)\
**Post date:** [July 21, 2016, 4:52pm UTC](https://discuss.elastic.co/t/rolling-restarts-issue/56118/4 "2016-07-21T16:52:09Z")

</div>

Also, I tried looking at the log already (in /var/log/elasticsearch). The only log file that is updated today only contains an error regarding getting the cluster health due to Shield expiration. I assume this would not affect a node being able to join a cluster, correct?

I see nothing else besides that in the log file.

---

<div class="post-metadata">

**Author:** ![jpcarey](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jpcarey/32/46668_2.png) [@jpcarey](https://discuss.elastic.co/u/jpcarey)\
**Post date:** [July 21, 2016, 4:59pm UTC](https://discuss.elastic.co/t/rolling-restarts-issue/56118/5 "2016-07-21T16:59:49Z")

</div>

No, the behavior of each plugins license expiration is documented. [https://www.elastic.co/guide/en/shield/current/license-management.html#license-management](https://www.elastic.co/guide/en/shield/current/license-management.html#license-management)

It is hard to say what exactly went wrong. You might find [this article](https://www.elastic.co/guide/en/elasticsearch/guide/current/_cluster_health.html) helpful in understanding your cluster health. However, with the shield license expired, cluster health, cluster stats, and index stats APIs are blocked. If you have a support subscription, you should reach out directly to get your license situation resolved and to further troubleshoot what went wrong in your cluster.

---

<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:** [July 5, 2017, 10:33pm UTC](https://discuss.elastic.co/t/rolling-restarts-issue/56118/6 "2017-07-05T22:33:37Z")

</div>