The tutorial at http://www.elasticsearch.org/tutorials/too-many-open-files/
If sudo -u elasticsearch -s "ulimit -Sn" shows 32000 but you
still have a low limit when you run ElasticSearch, you’re probably running it
through another program that doesn’t support PAM: a frequent offender is
[I have no way to know I'm running through supervisord, since I'm just typing the ./elasticsearch -f into a terminal on Ubuntu]
The only solution I know to this problem is to raise the nofile
limit for the user running supervisord, but this will obviously raise the limit
for all the processes running under supervisord, not an ideal situation.
Consider using the
service wrapper instead.
This is the service wrapper mentioned:
Is a service wrapper going to put this issue to bed?
Is there a way to ask ElasticSearch how many open files Lucene is using?
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to email@example.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAH6s0fyjTm%2BYN69PhgPSwObyJo6bbZa1Ac%2BzLK2J4i5oxyO5Zw%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.