# Azure Marketplace cluster - upgrade to 6.4.0
**URL:** https://discuss.elastic.co/t/azure-marketplace-cluster-upgrade-to-6-4-0/145929
**Category:** Elasticsearch
**Created:** [August 24, 2018, 2:28pm UTC](https://discuss.elastic.co/t/azure-marketplace-cluster-upgrade-to-6-4-0/145929 "2018-08-24T14:28:37Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@djl2](https://discuss.elastic.co/u/djl2)
#### Post date: [August 24, 2018, 2:28pm UTC](https://discuss.elastic.co/t/azure-marketplace-cluster-upgrade-to-6-4-0/145929/1 "2018-08-24T14:28:37Z")
Is there an ETA on when the Azure Marketplace cluster will be update to deploy 6.4.0? It's still is configured for v6.3.1.
> **[elastic/azure-marketplace](https://github.com/elastic/azure-marketplace)**
>
> azure-marketplace - Elasticsearch Azure Marketplace offering + ARM template
---
### Author:  [@forloop](https://discuss.elastic.co/u/forloop)
#### Post date: [August 27, 2018, 7:04am UTC](https://discuss.elastic.co/t/azure-marketplace-cluster-upgrade-to-6-4-0/145929/2 "2018-08-27T07:04:34Z")
Hey @djl2, No ETA on when the template will be updated; we will endeavour to update it as soon as we can.
---
### Author:  [@djl2](https://discuss.elastic.co/u/djl2)
#### Post date: [August 27, 2018, 10:35pm UTC](https://discuss.elastic.co/t/azure-marketplace-cluster-upgrade-to-6-4-0/145929/3 "2018-08-27T22:35:26Z")
Thanks Russ.
In the meantime, could you provide some guidance with upgrading the v6.3.1 cluster to v6.4? I had x-pack enabled on all nodes before I attempted a rolling upgrade. I followed this URL for guidance--
[https://www.elastic.co/guide/en/elasticsearch/reference/current/rolling-upgrades.html#rolling-upgrades](https://www.elastic.co/guide/en/elasticsearch/reference/current/rolling-upgrades.html#rolling-upgrades)
I just updated the master-0 node to v6.4. Now at ES service start up, this 'waiting' message is thrown in the logs.
[2018-08-27T21:46:03,353][INFO][o.e.n.Node] [ctesdmaster-0] started
[2018-08-27T21:46:03,420][INFO][o.e.x.m.e.l.LocalExporter] waiting for elected master node [{ctesdmaster-1}{5aIDf\_OfR6iOXeX-1Vmjzg}{BbeRU7LmSPihTmdU1Bx4wQ}{10.0.0.6}{10.0.0.6:9300}{update\_domain=0, fault\_domain=0, xpack.installed=true}] to setup local exporter [default\_local] (does it have x-pack installed?)
In Kibana Monitoring page is now failing as well. This error appears--
Monitoring Request Error
[search\_phase\_execution\_exception] all shards failed: Check the Elasticsearch
Monitoring cluster network connection or the load level of the nodes.
HTTP 503
Note I also tried updating all the nodes in another cluster (non-rolling) and had similar errors.
Note I'm currently using the x-pack trial version.
UPDATE: I rebooted the master-0 VM. The original 'waiting' message no longer appears in the log, but the error still exists in Kibana. Also, in ES-Head, I get the message "cluster health: red (25 of 27).
Thanks!
---
### Author:  [@forloop](https://discuss.elastic.co/u/forloop)
#### Post date: [August 27, 2018, 11:25pm UTC](https://discuss.elastic.co/t/azure-marketplace-cluster-upgrade-to-6-4-0/145929/4 "2018-08-27T23:25:12Z")
The process for upgrading a template deployment is no different from an [upgrade of Debian package to 6.4.0 running on Ubuntu 16.04](https://www.elastic.co/guide/en/elasticsearch/reference/current/setup-upgrade.html) anywhere, but note that the Elasticsearch deployment uses [monit](https://mmonit.com/) to monitor the Elasticsearch process, so Elasticsearch should be stopped with
```auto
sudo monit stop elasticsearch
```
and started with
```auto
sudo monit start elasticsearch
```
Going from 6.3.1 to 6.4.0, you'd be able to perform a rolling upgrade.
With Kibana, you'll need to stop the Kibana service with
```auto
sudo service kibana stop
```
update Kibana with 6.4.0 Debian package, then start again
```auto
sudo service kibana start
```
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [September 24, 2018, 11:25pm UTC](https://discuss.elastic.co/t/azure-marketplace-cluster-upgrade-to-6-4-0/145929/5 "2018-09-24T23:25:18Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.