# Rolling upgrade problem from 6.8 to 7.1.1

**URL:** <https://discuss.elastic.co/t/rolling-upgrade-problem-from-6-8-to-7-1-1/186571>\
**Category:** Elasticsearch\
**Created:** [June 20, 2019, 2:56am UTC](https://discuss.elastic.co/t/rolling-upgrade-problem-from-6-8-to-7-1-1/186571 "2019-06-20T02:56:47Z")\
**Posts on this page:** 1\
**Showing post:** 14

<div class="post-metadata">

**Author:** ![Peter\_LEE](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/peter_lee/32/48399_2.png) [@Peter\_LEE](https://discuss.elastic.co/u/Peter_LEE)\
**Post date:** [June 20, 2019, 9:36am UTC](https://discuss.elastic.co/t/rolling-upgrade-problem-from-6-8-to-7-1-1/186571/14 "2019-06-20T09:36:02Z")

</div>

I think my cluster didn't work yet. It didn't respond for REST API such as GET \_cat/nodes.

The other ES can't connect to the elected master. They just printed like this message.

> [2019-06-20T18:18:34,434][INFO][o.e.x.m.e.l.LocalExporter] [node-mdata-637] waiting for elected master node [{node-mdata-638}{UtHL00IMRzihkL\_erqCHPA}{wUWHEoNeRkK66PRZNoaGNg}{172.31.6.38}{172.31.6.38:9300}{ml.machine\_memory=33449705472, ml.max\_open\_jobs=20, xpack.installed=true}] to setup local exporter [default\_local] (does it have x-pack installed?)

And I found a error message

> [2019-06-20T18:39:05,786][WARN][o.e.n.Node] [node-mdata-637] timed out while waiting for initial discovery state - timeout: 30s

Why was this message printed even I set "cluster.publish.timeout: 90s" in elasticsearch.yml?

---

_[View the full topic](https://discuss.elastic.co/t/rolling-upgrade-problem-from-6-8-to-7-1-1/186571)._