# Unable to Join New node to existing cluster

**URL:** <https://discuss.elastic.co/t/unable-to-join-new-node-to-existing-cluster/314353>\
**Category:** Elasticsearch\
**Created:** [September 14, 2022, 1:36am UTC](https://discuss.elastic.co/t/unable-to-join-new-node-to-existing-cluster/314353 "2022-09-14T01:36:47Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![hiruni.insyncit.net](https://avatars.discourse-cdn.com/v4/letter/h/c68b51/32.png) [@hiruni.insyncit.net](https://discuss.elastic.co/u/hiruni.insyncit.net)\
**Post date:** [September 14, 2022, 1:36am UTC](https://discuss.elastic.co/t/unable-to-join-new-node-to-existing-cluster/314353/1 "2022-09-14T01:36:47Z")

</div>

Hi,

I'm using Elasticsearch 8.4 version.  
I was able to install Elasticsearch and Kibana.  
Then I tried to install on 2nd node.

I followed the steps in [https://www.elastic.co/guide/en/elasticsearch/reference/current/rpm.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/rpm.html)

But, after I installed Elasticsearch on 2nd node, it always creates as new cluster.

How can I avoid this issue..?

Thank You...!

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [September 14, 2022, 5:24am UTC](https://discuss.elastic.co/t/unable-to-join-new-node-to-existing-cluster/314353/2 "2022-09-14T05:24:07Z")

</div>

Please share your configuration and logs from one of these new nodes.

---

<div class="post-metadata">

**Author:** ![cheshirecat](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cheshirecat/32/109532_2.png) [@cheshirecat](https://discuss.elastic.co/u/cheshirecat)\
**Post date:** [September 14, 2022, 5:45am UTC](https://discuss.elastic.co/t/unable-to-join-new-node-to-existing-cluster/314353/3 "2022-09-14T05:45:42Z")

</div>

If it's `brand new` 😛 node you can create config with pointing other nodes and than use this tool:

```auto
cd /usr/share/elasticsearch/bin

```

and than:

```auto
sudo ./elasticsearch-node detach-cluster

```

But please be very careful - you're doing it at your own risk 🙂

---

<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:** [September 14, 2022, 7:04am UTC](https://discuss.elastic.co/t/unable-to-join-new-node-to-existing-cluster/314353/4 "2022-09-14T07:04:37Z")

</div>

> [@cheshirecat](#):
>
> But please be very careful - you're doing it at your own risk 🙂

It's not really enough to hint that there might be some risks here when the advice you've given is potentially very dangerous, leading to possible data loss, and is not at all correct either. There is never any need to `detach-cluster` on a brand-new node - the reference manual describes the [proper steps perform in that case](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-discovery-bootstrap-cluster.html#modules-discovery-bootstrap-cluster-joining). Even if this were good advice, I still recommend you also link to the [docs for the `elasticsearch-node` tool](https://www.elastic.co/guide/en/elasticsearch/reference/current/node-tool.html) which describe the risks in extensive detail.

---

<div class="post-metadata">

**Author:** ![cheshirecat](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cheshirecat/32/109532_2.png) [@cheshirecat](https://discuss.elastic.co/u/cheshirecat)\
**Post date:** [September 14, 2022, 7:11am UTC](https://discuss.elastic.co/t/unable-to-join-new-node-to-existing-cluster/314353/5 "2022-09-14T07:11:30Z")

</div>

When I was setting up my first cluster using Ansible I set it just like in manual with docs open at second screen. I tried for three days. There always was different cluster ids on each node (got three of them). Why? Probably tasks were completed in similar or even same time. That was the one and only way to add new node.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [September 14, 2022, 7:15am UTC](https://discuss.elastic.co/t/unable-to-join-new-node-to-existing-cluster/314353/6 "2022-09-14T07:15:39Z")

</div>

It'd be better to start a new topic on this avenue of discussion please, let's keep to the OPs problem.

---

<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:** [October 12, 2022, 7:16am UTC](https://discuss.elastic.co/t/unable-to-join-new-node-to-existing-cluster/314353/7 "2022-10-12T07:16:27Z")

</div>

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