# Upgrade from 6.4.3 to 7.1 erros in gce discovery **URL:** \ **Category:** Elasticsearch\ **Created:** [May 24, 2019, 3:22pm UTC](https://discuss.elastic.co/t/upgrade-from-6-4-3-to-7-1-erros-in-gce-discovery/182687 "2019-05-24T15:22:36Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![frankfoti](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/frankfoti/32/26965_2.png) [@frankfoti](https://discuss.elastic.co/u/frankfoti)\ **Post date:** [May 24, 2019, 3:22pm UTC](https://discuss.elastic.co/t/upgrade-from-6-4-3-to-7-1-erros-in-gce-discovery/182687/1 "2019-05-24T15:22:36Z")
This worked fine before the upgrade now getting error: [2019-05-24T15:21:02,699][DEBUG][o.e.a.a.c.s.TransportClusterStateAction] [rrc101-196516-elasticsearch-70test1] no known master node, scheduling a retry cluster.name: rrc101-196516-70tst node.name: rrc101-196516-elasticsearch-70test1 network.host: _gce_ node.master: true node.data: true node.ingest: true path.data: /mnt1/data path.logs: /mnt1/logs http.port: 9200 http.max\_content\_length: 2147483647B indices.memory.index\_buffer\_size: 30% bootstrap.memory\_lock: true action.destructive\_requires\_name: true xpack.monitoring.collection.enabled: true cloud: gce: project\_id: rrc101-196516 zone: ["us-east1-b", "us-east1-c", "us-east1-d"] discovery: zen.hosts\_provider: gce ffoti@rrc101-196516-elasticsearch-70test1:~$ ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [May 24, 2019, 3:57pm UTC](https://discuss.elastic.co/t/upgrade-from-6-4-3-to-7-1-erros-in-gce-discovery/182687/2 "2019-05-24T15:57:18Z")
Are there any other log messages? You should be seeing a warning message every 10 seconds or so too that's a bit more informative than the `DEBUG` message you quoted. I think you have skipped this vital step in the [full-cluster restart upgrade instructions](https://www.elastic.co/guide/en/elasticsearch/reference/7.1/restart-upgrade.html): > If upgrading from a 6.x cluster, you must [configure cluster bootstrapping](https://www.elastic.co/guide/en/elasticsearch/reference/7.1/modules-discovery-bootstrap-cluster.html) by setting the `cluster.initial_master_nodes` setting. ---
**Author:** ![frankfoti](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/frankfoti/32/26965_2.png) [@frankfoti](https://discuss.elastic.co/u/frankfoti)\ **Post date:** [May 24, 2019, 4:11pm UTC](https://discuss.elastic.co/t/upgrade-from-6-4-3-to-7-1-erros-in-gce-discovery/182687/3 "2019-05-24T16:11:19Z")
I reverted to non gce using this for now. See below. But... Our goal was to stay 100% gce "dynamic" discovery. Is that possible on the upgrade? We do not want to hard code IP's or Nodes in YML. Our install was doing that fine. We are scripting our installs and upgrades. Thanks for you quick feedback:) cluster.name: rrc101-196516-70tst node.name: rrc101-196516-elasticsearch-70test1 network.host: rrc101-196516-elasticsearch-70test1 node.master: true node.data: true node.ingest: true path.data: /mnt1/data path.logs: /mnt1/logs http.port: 9200 http.max\_content\_length: 2147483647B indices.memory.index\_buffer\_size: 30% bootstrap.memory\_lock: true action.destructive\_requires\_name: true xpack.monitoring.collection.enabled: true discovery.seed\_hosts: - rrc101-196516-elasticsearch-70test1 - rrc101-196516-elasticsearch-70test2 - rrc101-196516-elasticsearch-70test3 cluster.initial\_master\_nodes: - rrc101-196516-elasticsearch-70test1 - rrc101-196516-elasticsearch-70test2 - rrc101-196516-elasticsearch-70test3 ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [May 24, 2019, 4:16pm UTC](https://discuss.elastic.co/t/upgrade-from-6-4-3-to-7-1-erros-in-gce-discovery/182687/4 "2019-05-24T16:16:51Z")
> [@frankfoti](#): > > But... Our goal was to stay 100% gce "dynamic" discovery. Is that possible on the upgrade? We do not want to hard code IP's or Nodes in YML. Our install was doing that fine. We are scripting our installs and upgrades. You've got to help Elasticsearch out with the first election after the upgrade, because there's unfortunately no safe way to do this fully dynamically. Once the new cluster has formed you can drop the `cluster.initial_master_nodes` setting again. ---
**Author:** ![frankfoti](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/frankfoti/32/26965_2.png) [@frankfoti](https://discuss.elastic.co/u/frankfoti)\ **Post date:** [May 24, 2019, 5:43pm UTC](https://discuss.elastic.co/t/upgrade-from-6-4-3-to-7-1-erros-in-gce-discovery/182687/5 "2019-05-24T17:43:58Z")
Worked fine. We will add that to our process. Thanks ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [June 21, 2019, 5:44pm UTC](https://discuss.elastic.co/t/upgrade-from-6-4-3-to-7-1-erros-in-gce-discovery/182687/6 "2019-06-21T17:44:09Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.