# Rebuilding master node caused data loss

**URL:** https://discuss.elastic.co/t/rebuilding-master-node-caused-data-loss/23346
**Category:** Elasticsearch
**Created:** [April 21, 2015, 2:23pm UTC](https://discuss.elastic.co/t/rebuilding-master-node-caused-data-loss/23346 "2015-04-21T14:23:40Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![Brian1](https://avatars.discourse-cdn.com/v4/letter/b/50afbb/32.png) [@Brian1](https://discuss.elastic.co/u/Brian1)
#### Post date: [April 21, 2015, 2:23pm UTC](https://discuss.elastic.co/t/rebuilding-master-node-caused-data-loss/23346/1 "2015-04-21T14:23:40Z")

</div>

I have a cluster with 5 data nodes, and 1 master node. I decided to test a  
master node failure, and clearly I miss understood exactly what is stored  
on the master. I turned down the VM running the master node, and built a  
new one from scratch. I then added it to the cluster as a master. When  
this came online, I lost all my data that was in cluster previously and it  
started making new indexes clean again. Now this isn't critical data, this  
is my test setup, but it still confused me.

I have looked into this and it would seem there is a deafult setting for gateway.local.auto\_import\_dangled.  
As I understand it, this was put in place for people like me who didn't  
understand whta would happen if you lost a master node, and should by  
default have imported the old data from each data node. If this was  
defaulted to no, and just deleted the data, I would know exactly what  
happened. I have looked at my configurations and I haven't set this to no,  
and yet the data was deleted.

Can someone clarify if this setting is no longer valid, or if the default  
hsa been changd and not documented?

--  
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/bbfc97a6-a775-41f4-b34c-e38d7c2c515d%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/bbfc97a6-a775-41f4-b34c-e38d7c2c515d%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: [April 21, 2015, 8:19pm UTC](https://discuss.elastic.co/t/rebuilding-master-node-caused-data-loss/23346/2 "2015-04-21T20:19:13Z")

</div>

Default is still yes.

What happened in the logs on the data nodes?

On 22 April 2015 at 00:23, Brian [brian.sanders@gmail.com](mailto:brian.sanders@gmail.com) wrote:

> I have a cluster with 5 data nodes, and 1 master node. I decided to test  
> a master node failure, and clearly I miss understood exactly what is stored  
> on the master. I turned down the VM running the master node, and built a  
> new one from scratch. I then added it to the cluster as a master. When  
> this came online, I lost all my data that was in cluster previously and it  
> started making new indexes clean again. Now this isn't critical data, this  
> is my test setup, but it still confused me.
> 
> I have looked into this and it would seem there is a deafult setting for gateway.local.auto\_import\_dangled.  
> As I understand it, this was put in place for people like me who didn't  
> understand whta would happen if you lost a master node, and should by  
> default have imported the old data from each data node. If this was  
> defaulted to no, and just deleted the data, I would know exactly what  
> happened. I have looked at my configurations and I haven't set this to no,  
> and yet the data was deleted.
> 
> Can someone clarify if this setting is no longer valid, or if the default  
> hsa been changd and not documented?
> 
> --  
> 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/bbfc97a6-a775-41f4-b34c-e38d7c2c515d%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/bbfc97a6-a775-41f4-b34c-e38d7c2c515d%40googlegroups.com)  
> [https://groups.google.com/d/msgid/elasticsearch/bbfc97a6-a775-41f4-b34c-e38d7c2c515d%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/bbfc97a6-a775-41f4-b34c-e38d7c2c515d%40googlegroups.com?utm_medium=email&utm_source=footer)  
> .  
> For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

--  
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-EOhDGhU%3DHxWxWjOsPSTWu0YTRyyeK1CaGcMd4C0xsOg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X-EOhDGhU%3DHxWxWjOsPSTWu0YTRyyeK1CaGcMd4C0xsOg%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:18am UTC](https://discuss.elastic.co/t/rebuilding-master-node-caused-data-loss/23346/3 "2017-07-06T00:18:29Z")

</div>


