# Dangling index warning in elasticsearch

**URL:** https://discuss.elastic.co/t/dangling-index-warning-in-elasticsearch/82495
**Category:** Elasticsearch
**Created:** [April 16, 2017, 7:22am UTC](https://discuss.elastic.co/t/dangling-index-warning-in-elasticsearch/82495 "2017-04-16T07:22:05Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![Rupesh\_Ranjan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rupesh_ranjan/32/22283_2.png) [@Rupesh\_Ranjan](https://discuss.elastic.co/u/Rupesh_Ranjan)
#### Post date: [April 16, 2017, 7:22am UTC](https://discuss.elastic.co/t/dangling-index-warning-in-elasticsearch/82495/1 "2017-04-16T07:22:05Z")

</div>

I have deleted a few indices from Elasticsearch and I am seeing **dangling index** warning in my elasticsearch logs

> [2017-04-16T07:12:38,760][WARN][o.e.g.DanglingIndicesState] **[coordinate-node] [[trial-2017.03.29/jgEtpX6lROC0wwOgW-w0Vw]]** can not be imported as a **dangling index** , as an index with the same name and UUID exist in the index tombstones. This situation is likely caused by copying over the data directory for an index that was previously deleted.

Is that likely to cause any problem?  
If yes, how can i get rid of this warning.

P.S. I am using elasticsearch version 5.2.2.  
I am having 3 data nodes and 1 coordinate node with **discovery.zen.minimum\_master\_nodes: 2**

---

<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 17, 2017, 4:56am UTC](https://discuss.elastic.co/t/dangling-index-warning-in-elasticsearch/82495/2 "2017-04-17T04:56:48Z")

</div>

> [@Rupesh\_Ranjan](#):
>
> Is that likely to cause any problem?

No it won't, it'll take up a bit of disk space but that's about it.

---

<div class="post-metadata">

### Author: ![Rupesh\_Ranjan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rupesh_ranjan/32/22283_2.png) [@Rupesh\_Ranjan](https://discuss.elastic.co/u/Rupesh_Ranjan)
#### Post date: [April 17, 2017, 5:19am UTC](https://discuss.elastic.co/t/dangling-index-warning-in-elasticsearch/82495/3 "2017-04-17T05:19:58Z")

</div>

I have deleted logs of size in about GBs. If thats gonna occupy lot of disk space, is there any way to free up that disk space?

I generally use below to delete (via sense plugin for google chrome)

> DELETE /trial-2017.03.29

which i think is equivalent to curl -X DELETE http://"host-name":9200/trial-2017.03.29

---

<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 17, 2017, 6:04am UTC](https://discuss.elastic.co/t/dangling-index-warning-in-elasticsearch/82495/4 "2017-04-17T06:04:54Z")

</div>

Yep, that's correct.

To clean it up is a bit of a hassle unfortunately. Is this warning on your coordinating node?

---

<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: [May 15, 2017, 6:06am UTC](https://discuss.elastic.co/t/dangling-index-warning-in-elasticsearch/82495/5 "2017-05-15T06:06:01Z")

</div>

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