# Multiple same-named nodes in cluster and data is relocating (ES 1.7.5)

**URL:** <https://discuss.elastic.co/t/multiple-same-named-nodes-in-cluster-and-data-is-relocating-es-1-7-5/62080>\
**Category:** Elasticsearch\
**Created:** [October 3, 2016, 2:21pm UTC](https://discuss.elastic.co/t/multiple-same-named-nodes-in-cluster-and-data-is-relocating-es-1-7-5/62080 "2016-10-03T14:21:41Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![unknownunknown](https://avatars.discourse-cdn.com/v4/letter/u/4da419/32.png) [@unknownunknown](https://discuss.elastic.co/u/unknownunknown)\
**Post date:** [October 3, 2016, 2:21pm UTC](https://discuss.elastic.co/t/multiple-same-named-nodes-in-cluster-and-data-is-relocating-es-1-7-5/62080/1 "2016-10-03T14:21:41Z")

</div>

I run multiple instances of ES on the same system to obtain greater memory utilization (ES 1.7.5). Each instance has a different name (think host1-1, host1-2). Somehow, an additional instance of one of the nodes got started. The side effect of this is that ES decided to move data to that additional instance. When the cluster was restarted, it went red because there were only two instances. I've been able to manually recover either by manually moving the indices from the new node directory or by re-starting an extra third instance and relocating away from it.

Are there any practices I can use to prevent this from happening in the future?

---

<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:** [October 3, 2016, 8:05pm UTC](https://discuss.elastic.co/t/multiple-same-named-nodes-in-cluster-and-data-is-relocating-es-1-7-5/62080/2 "2016-10-03T20:05:52Z")

</div>

Config management and deployment with things like Puppet/Chef/Ansible.

---

<div class="post-metadata">

**Author:** ![unknownunknown](https://avatars.discourse-cdn.com/v4/letter/u/4da419/32.png) [@unknownunknown](https://discuss.elastic.co/u/unknownunknown)\
**Post date:** [October 4, 2016, 1:17pm UTC](https://discuss.elastic.co/t/multiple-same-named-nodes-in-cluster-and-data-is-relocating-es-1-7-5/62080/3 "2016-10-04T13:17:54Z")

</div>

I suppose my intended, more precise question would be, are there any mechanisms provided by elasticsearch that could help prevent the described problem state (either more than expected nodes and/or unwanted data relocation) from occurring?

---

<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:** [October 5, 2016, 8:19am UTC](https://discuss.elastic.co/t/multiple-same-named-nodes-in-cluster-and-data-is-relocating-es-1-7-5/62080/4 "2016-10-05T08:19:47Z")

</div>

Not in this sort of instance.

---

<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 5, 2017, 10:14pm UTC](https://discuss.elastic.co/t/multiple-same-named-nodes-in-cluster-and-data-is-relocating-es-1-7-5/62080/5 "2017-07-05T22:14:52Z")

</div>