Error when elasticsearch is started:
max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [262144]
It means that the value of the virtual memory limit is set too small, at least 262144
Temporary method:
sysctl -w vm.max_map_count=262144
Permanent method:
vim /etc/sysctl.conf
Add a row:
vm.max_map_count=262144
Update configuration
sysctl -p
Similar Posts:
- Elasticsearch startup error, bootstrap checks failed [How to Solve]
- Elasticsearch startup error, bootstrap checks failed
- [Solved] Elasticsearch Startup Error: node validation exception
- [Solved] ERROR: bootstrap checks failed memory locking requested for elasticsearch process but memory is not locked
- NPM Command Error: Allocation failed – JavaScript heap out of memory
- Eclipse failed to create the java virtual machine [How to Solve]
- odoo Wkhtmltopdf failed (error code: -11). Memory limit too low or maximum file number of subprocess reached. Message : b”
- eclipse.ini/myeclipse.ini -Xms,-Xmx,-PerSize
- About redis WARNING overcommit_ The solution of memory is set to 0
- [Solved] Nginx can’t listen to the problem of virtual VIP: 99: cannot assign requested address