Last Update: March 2020
Before you start reading this page, try the new Elasticsearch Check-Up - Get actionable recommendations that can improve your cluster search and indexing speed (no installation required).
Bootstrap Checks in Elasticsearch
Elasticsearch has many settings that can cause significant performance problems if not set correctly. To prevent this happening Elasticsearch will carry out what are known as bootstrap checks to ensure that these important settings have been covered. If any of the checks fail then elasticsearch will write an error to the logs and will not start.
Bootstrap checks are carried out when the network.host setting in
If network host is not set and you use the default localhost, then elasticsearch will consider the node to be in development mode, and bootstrap checks will not be enforced.
Common Issues with Bootstrap Checks
If you install elasticsearch using RPM or Debian packages (strongly recommended) then most of the important configuration is already done for you, and the only bootstrap checks you are likely to run up against are the following.
Heap size Check
The minimum and maximum heap sizes specified in jvm.options (or via environment variables) must be equal to one another.
Minimum file descriptors must have been set to at least 65535
Memory Lock Check
There are various methods used to prevent memory swapping, and you must use one of them. The most common is to set in elasticsearch.yml
For this to be effective you must give permission to elasticsearch to enable this. There are various ways to do so, depending upon your operating system.
Discovery Configuration Checks
At least one of the following properties must be configured in elasticsearch.yml to ensure that your node can form a cluster properly:
Less Common Bootstrap Check Issues
If you are not using RPM or debian packages, you may come across the following issues:
Max Number of Threads check
You must allow your system to create at least 4096 threads. In linux this is done by editing /etc/security/limits.conf and adjusting the nproc setting.
Max File Size check
Your system should be able to create unlimited file sizes. In linux this is done by editing /etc/security/limits.conf and adjusting the fsize setting
Max virtual memory check
The system should be able to create unlimited virtual memory for the elasticsearch user.
This is done by editing /etc/security/limits.conf
<user> - as unlimited
Max map count check
The system must be able to use mmap effectively. This is done by running the command
sysctl vm.max_map_count 262144
The following checks are also carried out, but are rarely found:
OsX File Descriptor Check Client Jvm Check UseS erial GC Check System Call Filter Check Might Fork Check On Error Check On Out Of Memory Error Check Early Access Check G1GC Check All Permission Check
Opster is redefining Elasticsearch management - pro-actively troubleshooting, optimizing performance, operating on clusters and assisting with all things needed to successfully run ES in production