# ES data loss on index deletion

**URL:** <https://discuss.elastic.co/t/es-data-loss-on-index-deletion/12387>\
**Category:** Elasticsearch\
**Created:** [June 12, 2013, 4:14pm UTC](https://discuss.elastic.co/t/es-data-loss-on-index-deletion/12387 "2013-06-12T16:14:06Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Anand\_Nalya](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/anand_nalya/32/571_2.png) [@Anand\_Nalya](https://discuss.elastic.co/u/Anand_Nalya)\
**Post date:** [June 12, 2013, 4:14pm UTC](https://discuss.elastic.co/t/es-data-loss-on-index-deletion/12387/1 "2013-06-12T16:14:06Z")

</div>

Hi,

I had around 70G of data across 40 indices in ES, I delete 36 of these  
indices using REST api (curl call). after that the 2 node cluster died and  
I was not able to restart the cluster. I had to delete the data directory.

Is this is a common scenario? Am I missing something or there is any  
specific way to delete multiple indices in quick succession.

Thanks,  
Anand

--  
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).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\
**Post date:** [June 16, 2013, 5:40pm UTC](https://discuss.elastic.co/t/es-data-loss-on-index-deletion/12387/2 "2013-06-16T17:40:29Z")

</div>

Hey,

do you have any more information than "the cluster died"? Have you checked  
your logfile and looked out for the exceptions? What happened on restarting  
when you increased the log level for more information?  
Did you simply delete the index, or did a delete-by-query which is going to  
cause a lot of IO and may render your system unresponsive (thus leading to  
dead cluster). Any more information would really help us a lot! Thanks!

--Alex

On Wed, Jun 12, 2013 at 6:14 PM, anand nalya [anand.nalya@gmail.com](mailto:anand.nalya@gmail.com) wrote:

> Hi,
> 
> I had around 70G of data across 40 indices in ES, I delete 36 of these  
> indices using REST api (curl call). after that the 2 node cluster died and  
> I was not able to restart the cluster. I had to delete the data directory.
> 
> Is this is a common scenario? Am I missing something or there is any  
> specific way to delete multiple indices in quick succession.
> 
> Thanks,  
> Anand
> 
> --  
> 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).  
> 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).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![Anand\_Nalya](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/anand_nalya/32/571_2.png) [@Anand\_Nalya](https://discuss.elastic.co/u/Anand_Nalya)\
**Post date:** [June 17, 2013, 5:37am UTC](https://discuss.elastic.co/t/es-data-loss-on-index-deletion/12387/3 "2013-06-17T05:37:04Z")

</div>

Hi Alex,

I deleted the complete mapping using the REST interface and not used a  
delete by query. Also, There was no time gap between these mapping deletion  
and I fired them one after another.

I haven't captured the log after the node failure but on restarting the  
cluster in foreground, it was printing some log messages regarding _trying  
to recove index\_name_

I know this is partial information, but still any help would be  
appreciated.

Also, what is that ideal way of deleting a lot of mappings from ES without  
running into IO issues?

Thanks,  
Anand

On Sunday, 16 June 2013 23:10:29 UTC+5:30, Alexander Reelsen wrote:

> Hey,
> 
> do you have any more information than "the cluster died"? Have you checked  
> your logfile and looked out for the exceptions? What happened on restarting  
> when you increased the log level for more information?  
> Did you simply delete the index, or did a delete-by-query which is going  
> to cause a lot of IO and may render your system unresponsive (thus leading  
> to dead cluster). Any more information would really help us a lot! Thanks!
> 
> --Alex
> 
> On Wed, Jun 12, 2013 at 6:14 PM, anand nalya \<[anand...@gmail.com](mailto:anand...@gmail.com)\<javascript:\>
> 
> > wrote:
> 
> > Hi,
> > 
> > I had around 70G of data across 40 indices in ES, I delete 36 of these  
> > indices using REST api (curl call). after that the 2 node cluster died and  
> > I was not able to restart the cluster. I had to delete the data directory.
> > 
> > Is this is a common scenario? Am I missing something or there is any  
> > specific way to delete multiple indices in quick succession.
> > 
> > Thanks,  
> > Anand
> > 
> > --  
> > 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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \<javascript:\>.  
> > 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).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [June 17, 2013, 6:06am UTC](https://discuss.elastic.co/t/es-data-loss-on-index-deletion/12387/4 "2013-06-17T06:06:43Z")

</div>

> Also, what is that ideal way of deleting a lot of mappings from ES without running into IO issues?

Delete the full index if you can. It is really really faster than deleting a mapping (means deleting all docs for this type). Basically, it's a rm -rf on each node which is extremly fast and frees your disk space immediatly.

## HTH

David 😉  
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 17 juin 2013 à 07:37, anand nalya [anand.nalya@gmail.com](mailto:anand.nalya@gmail.com) a écrit :

Hi Alex,

I deleted the complete mapping using the REST interface and not used a delete by query. Also, There was no time gap between these mapping deletion and I fired them one after another.

I haven't captured the log after the node failure but on restarting the cluster in foreground, it was printing some log messages regarding trying to recove index\_name

I know this is partial information, but still any help would be appreciated.

Also, what is that ideal way of deleting a lot of mappings from ES without running into IO issues?

Thanks,  
Anand

On Sunday, 16 June 2013 23:10:29 UTC+5:30, Alexander Reelsen wrote:

> Hey,
> 
> do you have any more information than "the cluster died"? Have you checked your logfile and looked out for the exceptions? What happened on restarting when you increased the log level for more information?  
> Did you simply delete the index, or did a delete-by-query which is going to cause a lot of IO and may render your system unresponsive (thus leading to dead cluster). Any more information would really help us a lot! Thanks!
> 
> --Alex
> 
> On Wed, Jun 12, 2013 at 6:14 PM, anand nalya [anand...@gmail.com](mailto:anand...@gmail.com) wrote:
> 
> > Hi,
> > 
> > I had around 70G of data across 40 indices in ES, I delete 36 of these indices using REST api (curl call). after that the 2 node cluster died and I was not able to restart the cluster. I had to delete the data directory.
> > 
> > Is this is a common scenario? Am I missing something or there is any specific way to delete multiple indices in quick succession.
> > 
> > ## Thanks, Anand
> > 
> > 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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.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).  
> > 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).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<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, 2:30am UTC](https://discuss.elastic.co/t/es-data-loss-on-index-deletion/12387/5 "2017-07-06T02:30:57Z")

</div>


