# Node not getting shards allocated back to it after upgrade

**URL:** <https://discuss.elastic.co/t/node-not-getting-shards-allocated-back-to-it-after-upgrade/186546>\
**Category:** Elasticsearch\
**Created:** [June 19, 2019, 9:20pm UTC](https://discuss.elastic.co/t/node-not-getting-shards-allocated-back-to-it-after-upgrade/186546 "2019-06-19T21:20:12Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![RayS](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rays/32/28268_2.png) [@RayS](https://discuss.elastic.co/u/RayS)\
**Post date:** [June 19, 2019, 9:20pm UTC](https://discuss.elastic.co/t/node-not-getting-shards-allocated-back-to-it-after-upgrade/186546/1 "2019-06-19T21:20:12Z")

</div>

I tried my hand at a roll update for my cluster. I have 3 nodes (elastic01,elastic02 and elastic03). Elastic03 is currently the master so I started with 02 first. That upgrade went fine and cluster rebuilt no problem. I then went to 01. Its been a half hour side I restarted.

Any thoughts

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [June 19, 2019, 10:47pm UTC](https://discuss.elastic.co/t/node-not-getting-shards-allocated-back-to-it-after-upgrade/186546/2 "2019-06-19T22:47:26Z")

</div>

Rather than deleting your question, it would be better if you could share your solution, as it may help others in the future with a similar problem 🙂

---

<div class="post-metadata">

**Author:** ![RayS](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rays/32/28268_2.png) [@RayS](https://discuss.elastic.co/u/RayS)\
**Post date:** [June 20, 2019, 4:44pm UTC](https://discuss.elastic.co/t/node-not-getting-shards-allocated-back-to-it-after-upgrade/186546/3 "2019-06-20T16:44:28Z")

</div>

The reason I withdrew the question is because it got worse. I thought I had updated one node and everything was going great. I was using the rolling upgrade/update instructions. However I ended up loosing the node that upgraded after I thought everything had stabilized. Through a series of unfortunate decisions on my part I'm now left with a 3 node cluster that will not accept new data and any time I create a new index. It shows up as red and you cannot write any documents to that index.

So I'm in a bit of a mess at the moment. I've never gotten the updates to work properly for me. I know this is something I either don't understand about the cluster or I'm missing a step.

If I do a \_cluster/health I get Active\_Primary\_nodes: 0 and Active\_shards: 0 but I have 3 data nodes.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [June 20, 2019, 8:40pm UTC](https://discuss.elastic.co/t/node-not-getting-shards-allocated-back-to-it-after-upgrade/186546/4 "2019-06-20T20:40:17Z")

</div>

Providing logs will be useful.  
What did you upgrade from, and to?

---

<div class="post-metadata">

**Author:** ![RayS](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rays/32/28268_2.png) [@RayS](https://discuss.elastic.co/u/RayS)\
**Post date:** [June 20, 2019, 9:31pm UTC](https://discuss.elastic.co/t/node-not-getting-shards-allocated-back-to-it-after-upgrade/186546/5 "2019-06-20T21:31:45Z")

</div>

Its fixed but here is what happened.

I did a curl -XGET 10.200.100.101:9200/\_cluster/allocation/explain?pretty

After reading through that I found out that all my nodes had "cluster.routing.allocation.enable": none. So yeah that was the problem. I set "cluster.routing.allocation.enable": "all" and everything came back.

So in summary after I went fro 7.0 to 7.1.1 on 02 and it looked liked everything balanced back out and was working. Then 02 disappeared. In the panic of having a node go missing I set them to none and then proceeded to make a lot of bad decisions by deleting indexes. Should have stopped in my tracks and troubleshot the node and not get all freaked out.

Completely my fault.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [June 20, 2019, 9:38pm UTC](https://discuss.elastic.co/t/node-not-getting-shards-allocated-back-to-it-after-upgrade/186546/6 "2019-06-20T21:38:13Z")

</div>

> [@RayS](#):
>
> Completely my fault.

Hey, that's ok! And it's super appreciated that you shared this info as it'll help someone in future.

---

<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:** [November 4, 2022, 7:13am UTC](https://discuss.elastic.co/t/node-not-getting-shards-allocated-back-to-it-after-upgrade/186546/7 "2022-11-04T07:13:02Z")

</div>


