# Dangling Index recovery and config

**URL:** <https://discuss.elastic.co/t/dangling-index-recovery-and-config/8092>\
**Category:** Elasticsearch\
**Created:** [June 13, 2012, 9:44pm UTC](https://discuss.elastic.co/t/dangling-index-recovery-and-config/8092 "2012-06-13T21:44:36Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mark\_D](https://avatars.discourse-cdn.com/v4/letter/m/48db29/32.png) [@Mark\_D](https://discuss.elastic.co/u/Mark_D)\
**Post date:** [June 13, 2012, 9:44pm UTC](https://discuss.elastic.co/t/dangling-index-recovery-and-config/8092/1 "2012-06-13T21:44:36Z")

</div>

Hi,

I have a two fold question. We are getting dangling indexes on a three  
machine, three node setup, and I dont understand why they are getting  
"dangled" I originally had this configuration, periodically I would  
get a dangling index. There are two indexes with a total of 20K docs.

gateway:  
type: fs  
fs:  
location: /var/lib/elasticsearch/gateway

index:  
number\_of\_shards: 2  
number\_of\_replicas: 1

I added this configuration thinking it would help, and it seemed to  
recover the indexes ok for a while, but now it is not

recover\_after\_nodes: 3  
recover\_after\_time: 5m  
expected\_nodes: 3

1. Is there a way to recover a dangling index in this scenario.
2. Any ideas why this would be happening with this configuration?

Thanks in advance.

Mark

---

<div class="post-metadata">

**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\
**Post date:** [June 14, 2012, 9:50pm UTC](https://discuss.elastic.co/t/dangling-index-recovery-and-config/8092/2 "2012-06-14T21:50:28Z")

</div>

Why are you using shared FS gateway, is that a location shared by the 3  
nodes? Just use the (default) local gateway.

On Wed, Jun 13, 2012 at 11:44 PM, Mark D [mark.a.donnelly@gmail.com](mailto:mark.a.donnelly@gmail.com) wrote:

> Hi,
> 
> I have a two fold question. We are getting dangling indexes on a three  
> machine, three node setup, and I dont understand why they are getting  
> "dangled" I originally had this configuration, periodically I would  
> get a dangling index. There are two indexes with a total of 20K docs.
> 
> gateway:  
> type: fs  
> fs:  
> location: /var/lib/elasticsearch/gateway
> 
> index:  
> number\_of\_shards: 2  
> number\_of\_replicas: 1
> 
> I added this configuration thinking it would help, and it seemed to  
> recover the indexes ok for a while, but now it is not
> 
> recover\_after\_nodes: 3  
> recover\_after\_time: 5m  
> expected\_nodes: 3
> 
> 1. Is there a way to recover a dangling index in this scenario.
> 2. Any ideas why this would be happening with this configuration?
> 
> Thanks in advance.
> 
> Mark

---

<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, 3:24am UTC](https://discuss.elastic.co/t/dangling-index-recovery-and-config/8092/3 "2017-07-06T03:24:04Z")

</div>

Closed on July 6, 2017, 3:24am UTC