# ES upgrade from 6.8.1 to 7.4.2

**URL:** <https://discuss.elastic.co/t/es-upgrade-from-6-8-1-to-7-4-2/217703>\
**Category:** Elasticsearch\
**Created:** [February 3, 2020, 10:13pm UTC](https://discuss.elastic.co/t/es-upgrade-from-6-8-1-to-7-4-2/217703 "2020-02-03T22:13:28Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![satya06](https://avatars.discourse-cdn.com/v4/letter/s/a6a055/32.png) [@satya06](https://discuss.elastic.co/u/satya06)\
**Post date:** [February 3, 2020, 10:13pm UTC](https://discuss.elastic.co/t/es-upgrade-from-6-8-1-to-7-4-2/217703/1 "2020-02-03T22:13:29Z")

</div>

Hello,  
I am trying to upgrade my TST environment from Elasticsearch 6.8.1 to 7.4.2, I am getting the below error during the upgrade in logs.  
Error:  
master not discovered yet, this node has not previously joined a bootstrapped (v7+) cluster, and this node must discover master-eligible nodes [hostnamenode1, hostnamenode2, hostnamenode3] to bootstrap a cluster: have discovered

elasticsearch.yml  
network.host: ipaddress of 1stvirtual

discovery.seed\_hosts: ["ipaddress of 2ndvirtual", "ipaddress of 3rdvirtual"]

discovery.zen.minimum\_master\_nodes: 3

cluster.initial\_master\_nodes: ["hostnamenode1", "hostnamenode2", "hostnamenode3"]

on each virtual server we are running 3 nodes...  
can you please help us with proper elasticsearch.yml configuration in this regard.

---

<div class="post-metadata">

**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:** [February 4, 2020, 1:26am UTC](https://discuss.elastic.co/t/es-upgrade-from-6-8-1-to-7-4-2/217703/2 "2020-02-04T01:26:09Z")

</div>

Does [this note in the docs](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-discovery-bootstrap-cluster.html#modules-discovery-bootstrap-cluster-fqdns) describe your problem, and its solution?

If not, you'll need to share some more detail. You haven't shared the full log message, and the bit that you have shared looks like it's been modified. Unfortunately the details of this message are important, and by modifying them you have likely lost the information that will help us solve your problem.

---

<div class="post-metadata">

**Author:** ![Magnus\_Kessler](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnus_kessler/32/42001_2.png) [@Magnus\_Kessler](https://discuss.elastic.co/u/Magnus_Kessler)\
**Post date:** [February 4, 2020, 10:18am UTC](https://discuss.elastic.co/t/es-upgrade-from-6-8-1-to-7-4-2/217703/3 "2020-02-04T10:18:49Z")

</div>

> [@satya06](#):
>
> on each virtual server we are running 3 nodes...

How did you configure the [`discovery.seed_hosts`](https://www.elastic.co/guide/en/elasticsearch/reference/current/discovery-settings.html#unicast.hosts)? With more than one node per physical server, these will listen on different ports. Try adding the transport protocol port (e.g. `9300`, `9301`, etc.) to each of the entries.

---

<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:** [March 3, 2020, 10:18am UTC](https://discuss.elastic.co/t/es-upgrade-from-6-8-1-to-7-4-2/217703/4 "2020-03-03T10:18:58Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.