# Problem occured with same name of cluster in different machines

**URL:** <https://discuss.elastic.co/t/problem-occured-with-same-name-of-cluster-in-different-machines/23710>\
**Category:** Elasticsearch\
**Created:** [May 28, 2015, 5:12pm UTC](https://discuss.elastic.co/t/problem-occured-with-same-name-of-cluster-in-different-machines/23710 "2015-05-28T17:12:09Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mehmet\_Ozer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mehmet_ozer/32/81567_2.png) [@Mehmet\_Ozer](https://discuss.elastic.co/u/Mehmet_Ozer)\
**Post date:** [May 28, 2015, 5:12pm UTC](https://discuss.elastic.co/t/problem-occured-with-same-name-of-cluster-in-different-machines/23710/1 "2015-05-28T17:12:09Z")

</div>

Hello,

I have a weird issue today and it gives me lots of problem. I had two  
cluster different but unfortunatelly I gave them the same names by mistake;

lets say;  
test\_cluster

- both cluster have had totaly different machines ( it was working well  
its been one month)
- today I added a machine in one of the cluster and I saw that all the  
machines were in the same cluster physically (it was not the case before  
adding the machine)
- I have chacked the unicast list; there were no machine in common

So someone can explain me how I had this problem and how I can seperate  
them ?

Thank you

## -- Please update your bookmarks! We have moved to [https://discuss.elastic.co/](https://discuss.elastic.co/)

You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/a3b29cb4-360f-4fea-9514-2dd90d25a682%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/a3b29cb4-360f-4fea-9514-2dd90d25a682%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<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:** [May 28, 2015, 9:54pm UTC](https://discuss.elastic.co/t/problem-occured-with-same-name-of-cluster-in-different-machines/23710/2 "2015-05-28T21:54:01Z")

</div>

This is why -

> **[Discovery | Elastic Docs](https://www.elastic.co/docs/deploy-manage/distributed-architecture/discovery-cluster-formation/discovery-hosts-providers)**
>
> Discovery is the process by which the cluster formation module finds other nodes with which to form a cluster. This process runs when you start an Elasticsearch...

Your best option is to use

> **[Index-level shard allocation | Elastic Docs](https://www.elastic.co/docs/deploy-manage/distributed-architecture/shard-allocation-relocation-recovery/index-level-shard-allocation)**
>
> In Elasticsearch, per-index settings allow you to control the allocation of shards to nodes through index-level shard allocation settings. These settings...

and then move indices to their correct node, then shutdown one cluster and  
change the cluster name.

PS - We're moving to [https://discuss.elastic.co/](https://discuss.elastic.co/), please join us there for  
any future discussions!

On 29 May 2015 at 03:12, mehmet özer [mehmetozer1988@gmail.com](mailto:mehmetozer1988@gmail.com) wrote:

> Hello,
> 
> I have a weird issue today and it gives me lots of problem. I had two  
> cluster different but unfortunatelly I gave them the same names by mistake;
> 
> lets say;  
> test\_cluster
> 
> - both cluster have had totaly different machines ( it was working  
> well its been one month)
> - today I added a machine in one of the cluster and I saw that all the  
> machines were in the same cluster physically (it was not the case before  
> adding the machine)
> - I have chacked the unicast list; there were no machine in common
> 
> So someone can explain me how I had this problem and how I can seperate  
> them ?
> 
> Thank you
> 
> ## -- Please update your bookmarks! We have moved to [https://discuss.elastic.co/](https://discuss.elastic.co/)
> 
> You received this message because you are subscribed to the Google Groups  
> "elasticsearch" group.  
> To unsubscribe from this group and stop receiving emails from it, send an  
> email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> To view this discussion on the web visit  
> [https://groups.google.com/d/msgid/elasticsearch/a3b29cb4-360f-4fea-9514-2dd90d25a682%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/a3b29cb4-360f-4fea-9514-2dd90d25a682%40googlegroups.com)  
> [https://groups.google.com/d/msgid/elasticsearch/a3b29cb4-360f-4fea-9514-2dd90d25a682%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/a3b29cb4-360f-4fea-9514-2dd90d25a682%40googlegroups.com?utm_medium=email&utm_source=footer)  
> .  
> For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

## -- Please update your bookmarks! We have moved to [https://discuss.elastic.co/](https://discuss.elastic.co/)

You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAEYi1X-q3V5xDDPg8HXC0dSZ3DoWxRTWjZF90Z-w4Ag3mC2vTA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X-q3V5xDDPg8HXC0dSZ3DoWxRTWjZF90Z-w4Ag3mC2vTA%40mail.gmail.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<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 6, 2017, 12:11am UTC](https://discuss.elastic.co/t/problem-occured-with-same-name-of-cluster-in-different-machines/23710/3 "2017-07-06T00:11:10Z")

</div>


