Shulou(Shulou.com)06/01 Report--

In this issue, the editor will bring you a summary of the problems of ElasticSearch startup failure and what are the solutions. The article is rich in content and analyzes and describes for you from a professional point of view. I hope you can get something after reading this article.

1.Java HotSpot (TM) 64-Bit Server VM warning: INFO: os::commit_memory (0x0000000085330000, 2060255232, 0) failed; error='Cannot allocate memory' (errno=12)

Since the default jvm space allocated by elasticsearch6.0 is 2g, modify the jvm space allocation

Vi elasticsearch/config/jvm.options

#-Xms1g

#-Xmx1g

Modify to

-Xms512m

-Xmx512m

2.max number of threads [2048] for user [elasticsearch] is too low, increase to at least [4096]

Modify / etc/security/limits.d/90-nproc.conf

* soft nproc 2048

Modify to

* soft nproc 4096

3.ERROR: bootstrap checks failed

Max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [262144]

Modify / etc/sysctl.conf configuration file

Vi / etc/sysctl.conf

Modify the following line:

Vm.max_map_count=262144

If it does not exist, add:

Echo "vm.max_map_count=262144" > > / etc/sysctl.conf

4.max file descriptors [65535] for elasticsearch process likely too low, increase to at least [65536]

Ulimit-n 65536

Then log out of the current user and take effect after logging in again

The above is the summary and solution of the ElasticSearch startup failure problem shared by the editor. If you happen to have similar doubts, please refer to the above analysis to understand. If you want to know more about it, you are welcome to follow the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.