Limited Time Offer!

For Less Than the Cost of a Starbucks Coffee, Access All DevOpsSchool Videos on YouTube Unlimitedly.
Master DevOps, SRE, DevSecOps Skills!

Enroll Now

Elastic Search Error – max file descriptors [4096] for elasticsearch process is too low, increase to at least [65535]

elastic-search-error-max-max-file-descriptors

Elastic Search Error – max file descriptors [4096] for elasticsearch process is too low, increase to at least [65535]

[2019-07-11T10:55:11,630][INFO ][o.e.t.TransportService   ] [es-client01] publish_address {172.31.11.126:9300}, bound_addresses {172.31.11.126:9300}
[2019-07-11T10:55:11,637][INFO ][o.e.b.BootstrapChecks    ] [es-client01] bound or publishing to a non-loopback address, enforcing bootstrap checks
ERROR: [2] bootstrap checks failed
[1]: max file descriptors [4096] for elasticsearch process is too low, increase to at least [65535]
[2]: max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [262144]

Solution

Temporary to the current login session
To set ulimit value on a parameter use the below command.
$ ulimit -p 65535

Persistent limits can be set for a particular user – By editing the /etc/security/limits.conf file. To set the maximum number of open files for the elasticsearch user to 65,536, add the following line to the limits.conf file:

vi /etc/security/limits.conf
------
ec2-user  -  nofile  65535
----

#This change will only take effect the next time the ec2-user user opens a new session.
  • https://gerardnico.com/os/linux/limits.conf
  • https://www.thegeekdiary.com/understanding-etc-security-limits-conf-file-to-set-ulimit/
Rajesh Kumar
Follow me
Latest posts by Rajesh Kumar (see all)
Subscribe
Notify of
guest
0 Comments
Newest
Oldest Most Voted
Inline Feedbacks
View all comments
0
Would love your thoughts, please comment.x
()
x