# MAX\_OPEN\_FILES value?

**URL:** <https://discuss.elastic.co/t/max-open-files-value/40747>\
**Category:** Elasticsearch\
**Created:** [February 2, 2016, 3:20pm UTC](https://discuss.elastic.co/t/max-open-files-value/40747 "2016-02-02T15:20:15Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![CraigFoote](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/craigfoote/32/4571_2.png) [@CraigFoote](https://discuss.elastic.co/u/CraigFoote)\
**Post date:** [February 2, 2016, 3:20pm UTC](https://discuss.elastic.co/t/max-open-files-value/40747/1 "2016-02-02T15:20:15Z")

</div>

Our elasticsearch is in a red state. It was trying to allocate shards but some of our nodes were reporting many "too many open files" errors and the sharding process seemed to stall. I've seen that the recommended size for this /etc/init.d/elasticsearch variable is 65536 which is what we were set to. We increased it to 131070 and restarted the services. The sharding process restarted and is counting down but I have no way of knowing yet whether it will succeed.

What do you have your MAX\_OPEN\_FILES set to?

Any advice?

Craig

---

<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 5, 2017, 11:19pm UTC](https://discuss.elastic.co/t/max-open-files-value/40747/2 "2017-07-05T23:19:36Z")

</div>

Closed on July 5, 2017, 11:19pm UTC