# Master node does not allow updating

**URL:** https://discuss.elastic.co/t/master-node-does-not-allow-updating/384028
**Category:** Elasticsearch
**Created:** [December 12, 2025, 6:23pm UTC](https://discuss.elastic.co/t/master-node-does-not-allow-updating/384028 "2025-12-12T18:23:35Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![juancamiloll](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/juancamiloll/32/110326_2.png) [@juancamiloll](https://discuss.elastic.co/u/juancamiloll)
#### Post date: [December 12, 2025, 6:23pm UTC](https://discuss.elastic.co/t/master-node-does-not-allow-updating/384028/1 "2025-12-12T18:23:35Z")

</div>

I am currently upgrading from the highest available version, v 8.19.3, to v 8.19.8.

I successfully completed the process on two of the three servers in the cluster, but now I am having problems with the one that acts as the masternode. When I stop the Elasticsearch service from monitoring, it still appears as online, and errors begin to appear from Kibana.

I would appreciate it if you could share a command to run from devtools to remove it from the executables as a master node while I manage to update it.

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/6/2/622cd7f13c224e3cc0cde462b0fcc7263e678b6e.png)

---

<div class="post-metadata">

### Author: ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)
#### Post date: [December 12, 2025, 6:43pm UTC](https://discuss.elastic.co/t/master-node-does-not-allow-updating/384028/2 "2025-12-12T18:43:13Z")

</div>

Commands on Kibana DevTools will be sent to the nodes configured in `kibana.yml`.

Which nodes are configured in Kibana?

---

<div class="post-metadata">

### Author: ![juancamiloll](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/juancamiloll/32/110326_2.png) [@juancamiloll](https://discuss.elastic.co/u/juancamiloll)
#### Post date: [December 12, 2025, 7:06pm UTC](https://discuss.elastic.co/t/master-node-does-not-allow-updating/384028/3 "2025-12-12T19:06:57Z")

</div>

> elasticsearch.hosts: ['[https://172.26.6.36:9200](https://172.26.6.36:9200)','[https://172.26.6.37:9200](https://172.26.6.37:9200)','[https://172.26.6.38:9200](https://172.26.6.38:9200)']

---

<div class="post-metadata">

### Author: ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)
#### Post date: [December 12, 2025, 7:10pm UTC](https://discuss.elastic.co/t/master-node-does-not-allow-updating/384028/4 "2025-12-12T19:10:45Z")

</div>

It should try the other nodes.

But just to confirm, you have just one node as master? If so your cluster will not be available until the node is up again.
