# Accidently started second instance resulting in duplicate node folders **URL:** \ **Category:** Elasticsearch\ **Created:** [December 11, 2013, 10:36am UTC](https://discuss.elastic.co/t/accidently-started-second-instance-resulting-in-duplicate-node-folders/14813 "2013-12-11T10:36:11Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Luk\_Morbee](https://avatars.discourse-cdn.com/v4/letter/l/ec9cab/32.png) [@Luk\_Morbee](https://discuss.elastic.co/u/Luk_Morbee)\ **Post date:** [December 11, 2013, 10:36am UTC](https://discuss.elastic.co/t/accidently-started-second-instance-resulting-in-duplicate-node-folders/14813/1 "2013-12-11T10:36:11Z")
Hi, We have a cluster of 2 nodes each with their own volume. On one of the nodes we accidentally started a second instance which resulted in duplicate node folders (0 & 1). The instance pointing to the nodes/0 folder was stopped. So the current instance is pointing to the nodes/1 folder. How do we rectify this? Would the following work? - ``` Stop the node ``` - ``` Delete the nodes/0 folder ``` - ``` Rename the nodes/1 folder to nodes/0 ``` - ``` Start the node again ``` Or are we better off stopping the node, remove all its content, and start it up again so that it syncs from scratch with the second node? Thx Luk Morbee -- 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/CAFfMV4PZ13%2Bg7t2ToztQuE8KRagnN-DKRhDAXtjUhpTBzwztgA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAFfMV4PZ13%2Bg7t2ToztQuE8KRagnN-DKRhDAXtjUhpTBzwztgA%40mail.gmail.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Jaguar](https://avatars.discourse-cdn.com/v4/letter/j/4af34b/32.png) [@Jaguar](https://discuss.elastic.co/u/Jaguar)\ **Post date:** [December 13, 2013, 1:15am UTC](https://discuss.elastic.co/t/accidently-started-second-instance-resulting-in-duplicate-node-folders/14813/2 "2013-12-13T01:15:48Z")
Hi, Allowing multiple directories in nodes/ by design. From my experience, you could stop the additional instance when the cluster state is green. But before doing that, you should make sure the instances are actually in a same cluster, and find out the correct process, which is using nodes/1 in your case. If you stop a wrong process, you will find yourself some data _missing_ next time you restart the cluster. The data isn't missing, just in different nodes/x directory. Cheers! 在 2013-12-11 下午6:36，"Luk Morbee" [luk.morbee@gmail.com](mailto:luk.morbee@gmail.com)写道： > Hi, > > We have a cluster of 2 nodes each with their own volume. On one of the > nodes we accidentally started a second instance which resulted in duplicate > node folders (0 & 1). The instance pointing to the nodes/0 folder was > stopped. So the current instance is pointing to the nodes/1 folder. > > How do we rectify this? > > Would the following work? > > - > > ``` > Stop the node > > ``` > > - > > ``` > Delete the nodes/0 folder > > ``` > > - > > ``` > Rename the nodes/1 folder to nodes/0 > > ``` > > - > > ``` > Start the node again > > ``` > > Or are we better off stopping the node, remove all its content, and start > it up again so that it syncs from scratch with the second node? > > Thx > > Luk Morbee > > -- > 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/CAFfMV4PZ13%2Bg7t2ToztQuE8KRagnN-DKRhDAXtjUhpTBzwztgA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAFfMV4PZ13%2Bg7t2ToztQuE8KRagnN-DKRhDAXtjUhpTBzwztgA%40mail.gmail.com) > . > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- 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/CAP0hgQ1fQzJTnkeye3LyV8PoJGBZ9KMBA7Rtxkp8QANkk9po3A%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAP0hgQ1fQzJTnkeye3LyV8PoJGBZ9KMBA7Rtxkp8QANkk9po3A%40mail.gmail.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![ananth](https://avatars.discourse-cdn.com/v4/letter/a/dfb087/32.png) [@ananth](https://discuss.elastic.co/u/ananth)\ **Post date:** [December 13, 2013, 6:39am UTC](https://discuss.elastic.co/t/accidently-started-second-instance-resulting-in-duplicate-node-folders/14813/3 "2013-12-13T06:39:52Z")
Setting node.max\_local\_storage\_nodes: 1 in elasticsearch.yml will help to resolve this problem -- 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/cfaba942-a6ba-4ef0-99e5-15382d98d951%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/cfaba942-a6ba-4ef0-99e5-15382d98d951%40googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Luk\_Morbee](https://avatars.discourse-cdn.com/v4/letter/l/ec9cab/32.png) [@Luk\_Morbee](https://discuss.elastic.co/u/Luk_Morbee)\ **Post date:** [December 13, 2013, 1:52pm UTC](https://discuss.elastic.co/t/accidently-started-second-instance-resulting-in-duplicate-node-folders/14813/4 "2013-12-13T13:52:28Z")
Thank you all for the feedback. Setting node.max\_local\_storage\_nodes to 1 was what we were looking for. On Wednesday, December 11, 2013 11:36:11 AM UTC+1, Luk Morbee wrote: > Hi, > > We have a cluster of 2 nodes each with their own volume. On one of the > nodes we accidentally started a second instance which resulted in duplicate > node folders (0 & 1). The instance pointing to the nodes/0 folder was > stopped. So the current instance is pointing to the nodes/1 folder. > > How do we rectify this? > > Would the following work? > > - > > ``` > Stop the node > > ``` > > - > > ``` > Delete the nodes/0 folder > > ``` > > - > > ``` > Rename the nodes/1 folder to nodes/0 > > ``` > > - > > ``` > Start the node again > > ``` > > Or are we better off stopping the node, remove all its content, and start > it up again so that it syncs from scratch with the second node? > > Thx > > Luk Morbee -- 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/76305332-5b46-41ba-aae7-60d8e051592d%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/76305332-5b46-41ba-aae7-60d8e051592d%40googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**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, 2:01am UTC](https://discuss.elastic.co/t/accidently-started-second-instance-resulting-in-duplicate-node-folders/14813/5 "2017-07-06T02:01:25Z")