# Elastic Search reallly slow \[but SOLVED!\]

**URL:** <https://discuss.elastic.co/t/elastic-search-reallly-slow-but-solved/4737>\
**Category:** Elasticsearch\
**Created:** [June 30, 2011, 12:58am UTC](https://discuss.elastic.co/t/elastic-search-reallly-slow-but-solved/4737 "2011-06-30T00:58:58Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Marty1](https://avatars.discourse-cdn.com/v4/letter/m/278dde/32.png) [@Marty1](https://discuss.elastic.co/u/Marty1)\
**Post date:** [June 30, 2011, 12:58am UTC](https://discuss.elastic.co/t/elastic-search-reallly-slow-but-solved/4737/1 "2011-06-30T00:58:58Z")

</div>

Just in case this helps anybody.

I was seeing really nice elastic search response times and went to  
bring it into production. I wrote a /etc/init.d/es script and  
restarted with it. I was (accidentally) then running elasticsearch as  
root with an fd limit of 1024. The log file was spewing with 'too  
many files'. When I fixed that to use the user elasticsearch who has  
a high fd limit, things started working beautifully again.

---

<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, 4:02am UTC](https://discuss.elastic.co/t/elastic-search-reallly-slow-but-solved/4737/2 "2017-07-06T04:02:14Z")

</div>

Closed on July 6, 2017, 4:02am UTC