# Dangling Index with Shared FS Gateway

**URL:** <https://discuss.elastic.co/t/dangling-index-with-shared-fs-gateway/10466>\
**Category:** Elasticsearch\
**Created:** [January 23, 2013, 3:27am UTC](https://discuss.elastic.co/t/dangling-index-with-shared-fs-gateway/10466 "2013-01-23T03:27:42Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sicker](https://avatars.discourse-cdn.com/v4/letter/s/a6a055/32.png) [@Sicker](https://discuss.elastic.co/u/Sicker)\
**Post date:** [January 23, 2013, 3:27am UTC](https://discuss.elastic.co/t/dangling-index-with-shared-fs-gateway/10466/1 "2013-01-23T03:27:42Z")

</div>

I found that after restart elasticsearch (0.19.1). I found that the  
dangling index on local file system but in the NFS Gateway are still have  
the data so Can I recovery it back?

[2013-01-23 00:29:17,314][INFO][indices.store] [Plunderer]  
[\_river] dangling index, exists on local file system, but not in cluster  
metadata, scheduling to delete in [2h]  
[2013-01-23 00:29:17,315][INFO][indices.store] [Plunderer]  
[directory] dangling index, exists on local file system, but not in cluster  
metadata, scheduling to delete in [2h]  
[2013-01-23 00:29:17,315][INFO][indices.store] [Plunderer]  
[people] dangling index, exists on local file system, but not in cluster  
metadata, scheduling to delete in [2h]

--

---

<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:55am UTC](https://discuss.elastic.co/t/dangling-index-with-shared-fs-gateway/10466/2 "2017-07-06T02:55:03Z")

</div>

Closed on July 6, 2017, 2:55am UTC