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

This article introduces the relevant knowledge of "how to solve the problem of intranet IP access in elasticsearch". In the operation of actual cases, many people will encounter such a dilemma. Next, let the editor lead you to learn how to deal with these situations. I hope you can read it carefully and be able to achieve something!

Edit elasticsearch.yml and modify network.host: IP yourself

Finally, add:

Http.cors.enabled: true

Http.cors.allow-origin: "*"

There is a problem:

Bootstrap checks failed

1 、 max file descriptors [4096] for elasticsearch process is too low, increase to at least [65536]

Solution: edit / etc/security/limits.conf, append:

* soft nofile 65536

* hard nofile 65536

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

Solution: edit / etc/sysctl.conf, append vm.max_map_count=655360 save and execute sysctl-p

3 、 max number of threads [2048] for user [tongtech] is too low, increase to at least [4096]

Cause of error: the maximum number of threads that failed the elasticsearch user for startup check is too low

Solution: vim / etc/security/limits.d/90-nproc.conf changed 2048 to 4096 or greater

4 、 the default discovery settings are unsuitable for production use; at least one of [discovery.seed_hosts, discovery.seed_providers, cluster.initial_master_nodes] must be configured

Resolve:

Edit: elasticsearch.yml

Add: cluster.initial_master_nodes: ["node-1"]

This is the end of the content of "how to solve the problem of intranet IP access in elasticsearch". Thank you for your reading. If you want to know more about the industry, you can follow the website, the editor will output more high-quality practical articles for you!

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.