On this thread
@jasontedor pointed that the user wants "nproc" instead of "nofile", but the documentation says "nofile", here Configuring system settings | Elasticsearch Guide [master] | Elastic
On this thread
@jasontedor pointed that the user wants "nproc" instead of "nofile", but the documentation says "nofile", here Configuring system settings | Elasticsearch Guide [master] | Elastic
Hi! In the thread that you reference, the reporter is having trouble with the number of threads that the elasticsearch
user can create:
This message is arising from the maximum number of threads bootstrap check. For Elasticsearch not running under systemd
as a service, this limit is controlled by the nproc
limit. This is why I refer the user to nproc
there.
However, the page that you refer to regarding nofile
is referring to a different issue. Namely the fact that the elasticsearch
user also needs the ability to have a lot of file descriptors open. This is covered in the file descriptor bootstrap check. For Elasticsearch not running under systemd
as a service, this limit is controlled by the nofile
limit.
In short: the issue the user is running into is different than the situation covered by the docs that you link to.
I hope that helps!
It's been a while that I sent you that message, but if I remember correctly I landed on that docs page because of an error I was having - and changing nofile wasn't helping. But when I followed your advice on that thread, instead of the docs, it worked!
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
© 2020. All Rights Reserved - Elasticsearch
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant logo are trademarks of the Apache Software Foundation in the United States and/or other countries.