[1]: max file descriptors [4096] for elasticsearch process is too low, increase to at least [65536]
switch to root user, edit limits.conf to add the following content
vi /etc/security/limits.conf
* soft nofile 65536
* hard nofile 65536
[2]: max number of threads [3818] for user [es] is too low, increase to at least [4096] The
maximum number of threads is too low. Modify the configuration file etc/security/limits.conf and add configuration
* soft nproc 4096
* hard nproc 4096
[3]: max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [262144]
Modify the /etc/sysctl.conf file and add the configuration vm.max_map_count=262144
vi /etc/sysctl.conf
sysctl -p
Execute the command sysctl -pto take effect
[4]: system call filters failed to install; check the logs and fix your configuration or disable system call filters at your own risk
The cause of the problem: because Centos6 does not support SecComp, and ES5.2.1 defaults to bootstrap.system_call_filter for true detection, so the detection fails, and the failure directly causes ES to fail to start
Solution: configure bootstrap.system_call_filter to false in elasticsearch.yml, pay attention to the following under Memory:
bootstrap.memory_lock: false
bootstrap.system_call_filter: false