# High openfiles issue in more indices

**URL:** <https://discuss.elastic.co/t/high-openfiles-issue-in-more-indices/97785>\
**Category:** Elasticsearch\
**Created:** [August 21, 2017, 3:10pm UTC](https://discuss.elastic.co/t/high-openfiles-issue-in-more-indices/97785 "2017-08-21T15:10:40Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Balamurali](https://avatars.discourse-cdn.com/v4/letter/b/90db22/32.png) [@Balamurali](https://discuss.elastic.co/u/Balamurali)\
**Post date:** [August 21, 2017, 3:10pm UTC](https://discuss.elastic.co/t/high-openfiles-issue-in-more-indices/97785/1 "2017-08-21T15:10:41Z")

</div>

Hi ,

Now we are using Elasticsearch 1.3.7 (3 TB data) with one index and many types (more than 250 ). we are facing mapping conflicts as big blow for upgradation.

so we planning to change our ES architecture as **creating many index (more than 250 indices) with one type in each one index** (which recommended in further versions).

While testing these in preview stage servers, we are **facing more issues like high openfiles count , server load, Hgh heap utilization (resource utilization)**.

Please suggest steps can we do in configuration to overcome these issues (HIGH openfiles issues, resource utilization)

Please don't say upgrade, because we are working hard for it.

---

<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:** [September 18, 2017, 3:10pm UTC](https://discuss.elastic.co/t/high-openfiles-issue-in-more-indices/97785/2 "2017-09-18T15:10:54Z")

</div>

Closed on September 18, 2017, 3:10pm UTC

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