Closed dr0i closed 9 years ago
Despite our 82 GB Ram, at some point elasticsearch begins to swap, slowly but steadily. The cause is the linux OS which wants to be clever (see https://www.elastic.co/guide/en/elasticsearch/reference/current/setup-configuration.html#setup-configuration-memory). It's best practice to disallow swap for elasticsearch, which is possible but only in tight cooporation with the OS:
bootstrap.mlockall: true
ulimit -l unlimited
/etc/init.d/elasticsearch restart
It's of most importance to do the steps marked as root to do it as root, not just sudo.
root
sudo
Try: curl http://localhost:9200/_nodes/process?pretty |grep mlock, it should show true if it works.
curl http://localhost:9200/_nodes/process?pretty |grep mlock
true
Put ulimit -l unlimited into elasticsearch start script in init.d. Restarted. urled mlock , all true. Closing.
mlock
Despite our 82 GB Ram, at some point elasticsearch begins to swap, slowly but steadily. The cause is the linux OS which wants to be clever (see https://www.elastic.co/guide/en/elasticsearch/reference/current/setup-configuration.html#setup-configuration-memory). It's best practice to disallow swap for elasticsearch, which is possible but only in tight cooporation with the OS:
bootstrap.mlockall: true
into elasticserach.ymlulimit -l unlimited
/etc/init.d/elasticsearch restart
It's of most importance to do the steps marked as
root
to do it asroot
, not justsudo
.Try:
curl http://localhost:9200/_nodes/process?pretty |grep mlock
, it should showtrue
if it works.