ElasticSearch pit row Tips

Preface: Select the installation package, try to choose a rpm package to install, because some configuration inside, rpm package management will help you do a good job.
One problem: [1]: max file descriptors [4096] for elasticsearch process is too low, increase to at least [65536]<br/>[2]: max number of threads [1024] for user [es] is too low, increase to at least [4096]<br/>
The reason: Unable to create a local file problem, users can create a maximum number of files that are too small
Solution: Switch to the root user, limits.conf edit the configuration file, add something like the following:
vim /etc/security/limits.conf
add the following : Note * Do not remove the

* soft nofile 65536
* hard nofile 131072
* soft nproc 2048
* hard nproc 4096

Question two:max virtual memory areas vm.max_map_count [65530] likely too low, increase to at least [262144]

The reason: The maximum virtual memory area vm.max_map_count too low
Solution: Switch to the root user to modify the configuration the sysctl.conf
vi /etc/sysctl.conf
add the following configuration:
vm.max_map_count = 655360
and execute the command:
sysctl -p

Question three: system call filters failed to install; check the logs and fix your configuration or disable system call filters at your own risk<br/>
reason: because Centos6 does not support SecComp, and ES5.2.1 default bootstrap.system_call_filter detection to true, resulting in detection failure, after failure led directly to the ES can not start
Solution: Configure the elasticsearch.yml in bootstrap.system_call_filter is false, pay attention to the following in Memory:

bootstrap.memory_lock: false
bootstrap.system_call_filter: false

Guess you like

Origin blog.51cto.com/12126385/2430522
Row