# One or more replica shards open many files

**URL:** <https://discuss.elastic.co/t/one-or-more-replica-shards-open-many-files/149577>\
**Category:** Elasticsearch\
**Created:** [September 23, 2018, 8:06am UTC](https://discuss.elastic.co/t/one-or-more-replica-shards-open-many-files/149577 "2018-09-23T08:06:42Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jozsef\_Basa](https://avatars.discourse-cdn.com/v4/letter/j/f14d63/32.png) [@Jozsef\_Basa](https://discuss.elastic.co/u/Jozsef_Basa)\
**Post date:** [September 23, 2018, 8:06am UTC](https://discuss.elastic.co/t/one-or-more-replica-shards-open-many-files/149577/1 "2018-09-23T08:06:42Z")

</div>

Hi  
I have a 5 node ES (6.2.2) cluster for monitoring the performance of around 15 applications. The indices feed by logstash. I have a daily indices of each application. One of the indices (4 primary + 1 replica) which actually the biggest one always makes strange thing. One or more of its replicas shards open many files and uses a lot of disk space which ends up too many open files log enrty on one or more nodes. If I uses \_cat/shards/index\_name the output look like this:

index shard prirep state docs store ip node  
siapm-nagiosxi-jmx-2018.09.21 2 p STARTED 4066912 2.2gb 10.240.150.16 pracp1\_node2  
siapm-nagiosxi-jmx-2018.09.21 2 r STARTED 4066912 1.5gb 10.240.150.15 pracp2\_node4  
siapm-nagiosxi-jmx-2018.09.21 1 r STARTED 4067841 1.5gb 10.240.150.16 pracp1\_node2  
siapm-nagiosxi-jmx-2018.09.21 1 p STARTED 4067841 2.2gb 10.240.150.17 pracp2\_node3  
siapm-nagiosxi-jmx-2018.09.21 3 p STARTED 4064477 2.1gb 10.240.150.15 pracp2\_node4  
siapm-nagiosxi-jmx-2018.09.21 3 r STARTED 4064477 1.5gb 10.240.150.14 pracp1\_node1  
siapm-nagiosxi-jmx-2018.09.21 0 p STARTED 4066127 2.5gb 10.240.150.14 pracp1\_node1  
**siapm-nagiosxi-jmx-2018.09.21 0 r STARTED 4067861 15.8gb 10.240.150.17 pracp2\_node3**

In this case I have one strage replica but other times I have two or more. On pracp2\_node3 the open\_file\_descriptors steadely grows. Now I have a workaround.  
In case of old index I close the index and reopen it and I can see the /\_nodes/stats/process API that the open\_file\_descriptors count normalises. In case of the actual day index I throw away the replica with the number\_of\_replicas: 0 setting and then bring back the replica. After all replica initialized the disk usages and the open file count normalise.

Any idea?  
Thaks  
Jozsef

---

<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:** [October 21, 2018, 8:06am UTC](https://discuss.elastic.co/t/one-or-more-replica-shards-open-many-files/149577/2 "2018-10-21T08:06:44Z")

</div>

Closed on October 21, 2018, 8:06am UTC

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