# Cannot get nodes to join same cluster

**URL:** <https://discuss.elastic.co/t/cannot-get-nodes-to-join-same-cluster/183796>\
**Category:** Elasticsearch\
**Created:** [May 31, 2019, 10:45pm UTC](https://discuss.elastic.co/t/cannot-get-nodes-to-join-same-cluster/183796 "2019-05-31T22:45:55Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![perezjasonr](https://avatars.discourse-cdn.com/v4/letter/p/d2c977/32.png) [@perezjasonr](https://discuss.elastic.co/u/perezjasonr)\
**Post date:** [May 31, 2019, 10:45pm UTC](https://discuss.elastic.co/t/cannot-get-nodes-to-join-same-cluster/183796/1 "2019-05-31T22:45:55Z")

</div>

Ive been going in circles for days now cannot get these two nodes to join the same cluster, any help would be appreciated:

config for node 1:

```
cluster.name: my-elastic
node.name: node-1
path.data: /var/lib/elasticsearch
path.logs: /var/log/elasticsearch
network.host: 0.0.0.0
discovery.seed_hosts:
   - 598717Ubuntu1
   - 598717Ubuntu2
cluster.initial_master_nodes:
  - 598717Ubuntu1
  - 598717Ubuntu2
xpack.security.enabled: true
xpack.security.authc.realms.native.native1.order: 1

```

config for node 2:

```
cluster.name: my-elastic
node.name: node-2
path.data: /var/lib/elasticsearch
path.logs: /var/log/elasticsearch
network.host: 0.0.0.0
discovery.seed_hosts:
   - 598717Ubuntu1
   - 598717Ubuntu2
cluster.initial_master_nodes:
  - 598717Ubuntu1
  - 598717Ubuntu2
xpack.security.enabled: true
xpack.security.authc.realms.native.native1.order: 1

```

Its so strange. They can curl each other and bring up cluster info, so I know they can communicate. I even telnet'd using 9300. Is there something I'm missing?

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [June 1, 2019, 2:52am UTC](https://discuss.elastic.co/t/cannot-get-nodes-to-join-same-cluster/183796/2 "2019-06-01T02:52:51Z")

</div>

Please format your code, logs or configuration files using `</>` icon as explained in [this guide](https://discuss.elastic.co/t/about-the-elasticsearch-category/21) and not the citation button. It will make your post more readable.

Or use markdown style like:

````
```
CODE
```

````

This is the icon to use if you are not using markdown format:

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/7/e/7e6e239431ec2d71cbf1beef741f2e93e7cc762c.jpg)

There's a live preview panel for exactly this reasons.

Lots of people read these forums, and many of them will simply skip over a post that is difficult to read, because it's just too large an investment of their time to try and follow a wall of badly formatted text.  
If your goal is to get an answer to your questions, it's in your interest to make it as easy to read and understand as possible.  
Please update your post as the configuration is not really readable here.

---

<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 1, 2019, 9:20am UTC](https://discuss.elastic.co/t/cannot-get-nodes-to-join-same-cluster/183796/3 "2019-06-01T09:20:45Z")

</div>

This sounds like a duplicate of this recent post:

> [@\[SOLVED\] Don't succeed to create cluster ES 7.1](https://discuss.elastic.co/t/solved-dont-succeed-to-create-cluster-es-7-1/183690/10):
>
> Thanks. The three nodes all have distinct cluster UUIDs: "cluster\_uuid" : "Ki2hYWPYTH-XL3Fm6sIKxg", "cluster\_uuid" : "6CCZsxyYSJylB9P\_kujFlA", "cluster\_uuid" : "sRZoKEEDQZywbRU3qb8L0Q", This is probably because the first time they started up you were not using the config you quote above, and so they each formed a one-node cluster. You cannot merge separate clusters together. Instead you will need to start again from the beginning: wipe their data directories and restart them, and they sh…

---

<div class="post-metadata">

**Author:** ![perezjasonr](https://avatars.discourse-cdn.com/v4/letter/p/d2c977/32.png) [@perezjasonr](https://discuss.elastic.co/u/perezjasonr)\
**Post date:** [June 1, 2019, 11:16am UTC](https://discuss.elastic.co/t/cannot-get-nodes-to-join-same-cluster/183796/4 "2019-06-01T11:16:59Z")

</div>

thank you, that was exactly the problem. I wiped the data dir (actually I removed it entirely and had to recreate it and put the permissions back because it errored out), so for anyone else clear the dir contents dont actually remove the dir itself. once I did that, it attached to the cluster.

---

<div class="post-metadata">

**Author:** ![perezjasonr](https://avatars.discourse-cdn.com/v4/letter/p/d2c977/32.png) [@perezjasonr](https://discuss.elastic.co/u/perezjasonr)\
**Post date:** [June 1, 2019, 11:24am UTC](https://discuss.elastic.co/t/cannot-get-nodes-to-join-same-cluster/183796/5 "2019-06-01T11:24:57Z")

</div>

I have two other posts where I did actually do what you said, didn't think it was necessary for this one because it was just lines from my config file, ill do it in the future.

---

<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:** [June 29, 2019, 11:25am UTC](https://discuss.elastic.co/t/cannot-get-nodes-to-join-same-cluster/183796/6 "2019-06-29T11:25:01Z")

</div>

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