# Elastic Search 7.13.1 Cluster bootstrapping error

**URL:** <https://discuss.elastic.co/t/elastic-search-7-13-1-cluster-bootstrapping-error/275858>\
**Category:** Elasticsearch\
**Created:** [June 14, 2021, 2:57pm UTC](https://discuss.elastic.co/t/elastic-search-7-13-1-cluster-bootstrapping-error/275858 "2021-06-14T14:57:17Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![prithvirajsivarajan](https://avatars.discourse-cdn.com/v4/letter/p/8e8cbc/32.png) [@prithvirajsivarajan](https://discuss.elastic.co/u/prithvirajsivarajan)\
**Post date:** [June 14, 2021, 2:57pm UTC](https://discuss.elastic.co/t/elastic-search-7-13-1-cluster-bootstrapping-error/275858/1 "2021-06-14T14:57:17Z")

</div>

I configured two nodes on two Linux VMs and it is working. Currently trying to setup a third node on the cluster in my local windows machine. Getting the errors below

`````````````````````````````````````````````````````````auto

[node-3] failed to join {node-1}{3eMmu1kVQtuB95A1KX4cXQ}{2m4B33pgQPCN7B6oeZuaww}{ **.***. ***.*** }{ **.***. ***.*** :9300}{cdfhilmrstw}{ml.machine_memory=16599810048, ml.max_open_jobs=512, xpack.installed=true, ml.max_jvm_size=8300527616, transform.node=true} with JoinRequest{sourceNode={node-3}{gxNAxl-xQqirbIpQ30NXYQ}{9UhA-NSxTyqtcA0HbjAGzA}{ **.***. ***.*** }{ **.***. ***.*** :9300}{cdfhilmrstw}{ml.machine_memory=8442609664, xpack.installed=true, transform.node=true, ml.max_open_jobs=512, ml.max_jvm_size=1037959168}, minimumTerm=6, optionalJoin=Optional.empty}
org.elasticsearch.transport.RemoteTransportException: [node-1][**.***. ***.*** :9300][internal:cluster/coordination/join]

master not discovered yet, this node has not previously joined a bootstrapped (v7+) cluster, and this node must discover master-eligible nodes [**.***. ***.*** :9300] to bootstrap a cluster

````````````````````````````````````````````````````````
`````````````````````````````````````````````````````````

---

<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:** [June 14, 2021, 3:03pm UTC](https://discuss.elastic.co/t/elastic-search-7-13-1-cluster-bootstrapping-error/275858/2 "2021-06-14T15:03:58Z")

</div>

> [@prithvirajsivarajan](#):
>
> `this node must discover master-eligible nodes [**.***. ***.*** :9300] to bootstrap a cluster`

You have set `cluster.initial_master_nodes` but the [docs](https://www.elastic.co/guide/en/elasticsearch/reference/current/important-settings.html#initial_master_nodes) say:

> **IMPORTANT** : After the cluster forms successfully for the first time, remove the `cluster.initial_master_nodes` setting from each nodes' configuration. Do not use this setting when restarting a cluster or adding a new node to an existing cluster.

---

<div class="post-metadata">

**Author:** ![prithvirajsivarajan](https://avatars.discourse-cdn.com/v4/letter/p/8e8cbc/32.png) [@prithvirajsivarajan](https://discuss.elastic.co/u/prithvirajsivarajan)\
**Post date:** [June 14, 2021, 5:00pm UTC](https://discuss.elastic.co/t/elastic-search-7-13-1-cluster-bootstrapping-error/275858/3 "2021-06-14T17:00:33Z")

</div>

I commented out the cluster.initial\_master\_nodes from all the three nodes and tried running the windows machine node again. Now it says [cluster.initial\_master\_nodes] is empty on this node.

```auto
[node-3] master not discovered yet, this node has not previously joined a bootstrapped (v7+) cluster, and [cluster.initial_master_nodes] is empty on this node: have discovered [{node-3}{gxNAxl-xQqirbIpQ30NXYQ}{ZPvpYSMJS2qZ_jLOXubBpA}{ **.***. ***.*** }{ **.***. ***.*** :9300}{cdfhilmrstw}, {node-1}{y2WpONChR_WD3DgQYT1VXg}{dfY9UqqeRViIX3xv6IJuTQ}{ **.***. ***.*** }{ **.***. ***.*** :9300}{cdfhilmrstw}, {node-2}{L9EX348MSrypvQDxuTFMLQ}{uXev5N_FR7qGquhjlblZpw}{ **.***. ***.*** }{ **.***. ***.*** :9300}{cdfhilmrstw}]; discovery will continue using [**.***. ***.*** :9300, **.***. ***.*** :9300] from hosts providers and [{node-3}{gxNAxl-xQqirbIpQ30NXYQ}{ZPvpYSMJS2qZ_jLOXubBpA}{ **.***. ***.*** }{ **.***. ***.*** :9300}{cdfhilmrstw}] from last-known cluster state; node term 6, last-accepted version 0 in term 0
[2021-06-14T21:29:40,121][WARN][o.e.c.c.ClusterFormationFailureHelper] [node-3] master not discovered yet, this node has not previously joined a bootstrapped (v7+) cluster, and [cluster.initial_master_nodes] is empty on this node: have discovered [{node-3}{gxNAxl-xQqirbIpQ30NXYQ}{ZPvpYSMJS2qZ_jLOXubBpA}{ **.***. ***.*** }{ **.***. ***.*** :9300}{cdfhilmrstw}, {node-1}{y2WpONChR_WD3DgQYT1VXg}{dfY9UqqeRViIX3xv6IJuTQ}{ **.***. ***.*** }{ **.***. ***.*** :9300}{cdfhilmrstw}, {node-2}{L9EX348MSrypvQDxuTFMLQ}{uXev5N_FR7qGquhjlblZpw}{ **.***. ***.*** }{ **.***. ***.*** :9300}{cdfhilmrstw}]; discovery will continue using [**.***. ***.*** :9300, **.***. ***.*** :9300] from hosts providers and [{node-3}{gxNAxl-xQqirbIpQ30NXYQ}{ZPvpYSMJS2qZ_jLOXubBpA}{ **.***. ***.*** }{ **.***. ***.*** :9300}{cdfhilmrstw}] from last-known cluster state; node term 6, last-accepted version 0 in term 0
[2021-06-14T21:29:43,967][WARN][o.e.t.TransportService] [node-3] Received response for a request that has timed out, sent [3.3s/3317ms] ago, timed out [210ms/210ms] ago, action [internal:discovery/request_peers], node [{node-2}{L9EX348MSrypvQDxuTFMLQ}{uXev5N_FR7qGquhjlblZpw}{ **.***. ***.*** }{ **.***. ***.*** :9300}{cdfhilmrstw}{ml.machine_memory=16599810048, ml.max_open_jobs=512, xpack.installed=true, ml.max_jvm_size=8300527616, transform.node=true}], id [91]

```

---

<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:** [June 14, 2021, 5:19pm UTC](https://discuss.elastic.co/t/elastic-search-7-13-1-cluster-bootstrapping-error/275858/4 "2021-06-14T17:19:01Z")

</div>

Sounds good.

It's hard to tell what else is wrong from the few log messages you've shared. I think there will be other log messages that are more helpful. `Received response for a request that has timed out` indicates a timeout, maybe faulty network or maybe the nodes are overloaded.

---

<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:** [July 12, 2021, 5:19pm UTC](https://discuss.elastic.co/t/elastic-search-7-13-1-cluster-bootstrapping-error/275858/5 "2021-07-12T17:19:10Z")

</div>

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