# Duplicate nodes

**URL:** <https://discuss.elastic.co/t/duplicate-nodes/80432>\
**Category:** Elasticsearch\
**Created:** [March 29, 2017, 7:59am UTC](https://discuss.elastic.co/t/duplicate-nodes/80432 "2017-03-29T07:59:50Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Azfar](https://avatars.discourse-cdn.com/v4/letter/a/e95f7d/32.png) [@Azfar](https://discuss.elastic.co/u/Azfar)\
**Post date:** [March 29, 2017, 7:59am UTC](https://discuss.elastic.co/t/duplicate-nodes/80432/1 "2017-03-29T07:59:50Z")

</div>

We are on ElasticSearch 2.4.4.

Suddenly elasticsearch start writing duplicate data and after checking the logs and data we found that another instance of elasticseach was started by Monit ([https://mmonit.com/monit/](https://mmonit.com/monit/)) after a false detection.

Before that we have only one node directory "0" and now we are seeing another folder "1" and two different elastcisearch processes (ps aux). Both folders have identical data and all indexers operation are replicated on duplicate node as well hence doubled indexing time, disk consumption and processing.

I dont know what is it (a replica?) and how can I get rid of the duplicate one.

---

<div class="post-metadata">

**Author:** ![jpountz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jpountz/32/45836_2.png) [@jpountz](https://discuss.elastic.co/u/jpountz)\
**Post date:** [March 29, 2017, 8:25am UTC](https://discuss.elastic.co/t/duplicate-nodes/80432/2 "2017-03-29T08:25:59Z")

</div>

That "1" folder is created when multiple Elasticsearch instances are started on the same data directory. You should stop the instance that uses that "1" folder. If the cluster health remains green then it means all the data that this instance stored was also on other nodes, so you can remove that folder.

---

<div class="post-metadata">

**Author:** ![Azfar](https://avatars.discourse-cdn.com/v4/letter/a/e95f7d/32.png) [@Azfar](https://discuss.elastic.co/u/Azfar)\
**Post date:** [March 29, 2017, 9:16am UTC](https://discuss.elastic.co/t/duplicate-nodes/80432/3 "2017-03-29T09:16:15Z")

</div>

Thanks for clarification, I will try that.

Will "node.max\_local\_storage\_nodes: 1" help in future?

---

<div class="post-metadata">

**Author:** ![jpountz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jpountz/32/45836_2.png) [@jpountz](https://discuss.elastic.co/u/jpountz)\
**Post date:** [March 29, 2017, 9:43am UTC](https://discuss.elastic.co/t/duplicate-nodes/80432/4 "2017-03-29T09:43:23Z")

</div>

Yes it will.

---

<div class="post-metadata">

**Author:** ![Azfar](https://avatars.discourse-cdn.com/v4/letter/a/e95f7d/32.png) [@Azfar](https://discuss.elastic.co/u/Azfar)\
**Post date:** [March 29, 2017, 11:40am UTC](https://discuss.elastic.co/t/duplicate-nodes/80432/5 "2017-03-29T11:40:42Z")

</div>

Much appreciate your help.

---

<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:** [April 26, 2017, 11:40am UTC](https://discuss.elastic.co/t/duplicate-nodes/80432/6 "2017-04-26T11:40:57Z")

</div>

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