Elasticsearch is not starting when bootstrap.memory_lock is set to true
Elasticsearch throws following error when bootstrap.memory_lock is set to true,
bootstrap checks failed
memory locking requested for elasticsearch process but memory is not locked
Solution:
When using the RPM or Debian packages on systems that use systemd, system limits must be specified via systemd. The systemd service file (/usr/lib/systemd/system/elasticsearch.service) contains the limits that are applied by default.
To override them, add a file called /etc/systemd/system/elasticsearch.service.d/override.conf or you can run systemctl edit elasticsearch which opens the file automatically inside your default editor. Set any changes in this file, such as:
[Service]
LimitMEMLOCK=infinity
Once finished, reload units:
systemctl daemon-reload
Now start Elasticsearch.
systemctl start elasticsearch
0 Comments