In addition to Weibo, there is also WeChat
Please pay attention
WeChat public account
Shulou
2025-02-14 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Internet Technology >
Share
Shulou(Shulou.com)06/02 Report--
This article introduces the relevant knowledge of "the detailed installation process of Elasticsearch7.2 cluster". Many people will encounter such a dilemma in the operation of actual cases, so 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!
1. Configuration file
[root@es1 ~] # grep'^ [a-zA-Z]'/ etc/elasticsearch/elasticsearch.ymlcluster.name: xing-applicationnode.name: node-1path.data: / var/lib/elasticsearchpath.logs: / var/log/elasticsearchnetwork.host: 0.0.0.0cluster.initial_master_nodes: ["node-1"] http.cors.enabled: truehttp.cors.allow-origin: "*" discovery.seed_hosts: ["192.168.56.14", "192.168.56.15" "192.168.56.16"] [root@es1 ~] # [root@es2 ~] # grep'^ [a-zA-Z]'/ etc/elasticsearch/elasticsearch.ymlcluster.name: xing-applicationnode.name: node-2path.data: / var/lib/elasticsearchpath.logs: / var/log/elasticsearchnetwork.host: 0.0.0.0cluster.initial_master_nodes: ["node-1"] http.cors.enabled: truehttp.cors.allow-origin: "* "discovery.seed_hosts: [" 192.168.56.14 " "192.168.56.15" "192.168.56.16"] [root@es2 ~] # [root@es3 ~] # grep'^ [a-zA-Z]'/ etc/elasticsearch/elasticsearch.ymlcluster.name: xing-applicationnode.name: node-3path.data: / var/lib/elasticsearchpath.logs: / var/log/elasticsearchnetwork.host: 0.0.0.0cluster.initial_master_nodes: ["node-1"] http.cors.enabled: truehttp.cors.allow-origin: " * "discovery.seed_hosts: [" 192.168.56.14 " "192.168.56.15", "192.168.56.16"] [root@es3 ~] #
2. Installation command
Yum-y localinstall kibana-7.2.0-x86_64.rpm elasticsearch-7.2.0-x86_64.rpm
Reference download address
Https://www.elastic.co/cn/downloads/past-releases
3. Start the command
/ etc/init.d/elasticsearch start
4. Parameter description
Cluster.name: xing-application configures the cluster name of es. By default, elasticsearch,es will automatically discover es under the same IP address range. If there are multiple clusters under the same IP address range, you can use this attribute to distinguish different clusters. Node.name: node-1 node name, which is randomly assigned a name in the name list by default. The list is in the name.txt file in the config folder in es's jar package, with many interesting names added by the author. Path.data: / var/lib/elasticsearch sets the storage path for index data. The default is the data folder under the es root directory. You can set multiple storage paths separated by commas. Path.logs: / var/log/elasticsearch sets the storage path of log files. By default, the logs folder under the es root directory network.host: 0.0.0.0 sets the bound ip address, which can be the cluster.initial_master_nodes: ["node-1"] parameter of ipv4 or ipv6 and set the hostname or IP address of a series of nodes that meet the conditions of the master node to boot the startup cluster. Manually specify the name or ip of all nodes that can be mater, and these configurations will calculate http.cors.enabled in the first election: true if the HTTP port is enabled, this property specifies whether cross-domain REST requests are allowed. Http.cors.allow-origin: "*" if the value of http.cors.enabled is true, then this attribute specifies where the REST request is allowed to come from. Discovery.seed_hosts: ["192.168.56.14", "192.168.56.15", "192.168.56.16"] configure the host address of the cluster. After configuration, the hosts in the cluster can be automatically discovered.
Prevent brain fissure:
Discovery.zen.minimum_master_nodes= Cluster Node / 2room1
5. Final effect of cluster
6. Tar.gz installation error handling
6.1. Start the error report
Non-root is required to start the user. If you start it with root, you need to delete the root generation files under the logs and config directories.
6.2. Environment configuration error report
Error:
ERROR: [3] bootstrap checks failed [1]: max file descriptors [4096] for elasticsearch process is too low, increase to at least [65535] [2]: max number of threads [3869] for user [elasticsearch] is too low, increase to at least [4096] [3]: max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [262144]
Corresponding processing:
[1]: max file descriptors [4096] for elasticsearch process is too low, increase to at least [65535] [root@es1 ~] # cat / etc/sysctl.conf * soft nofile 65536 * hard nofile 65536 [2]: max number of threads [3869] for user [elasticsearch] is too low Increase to at least [4096] [root@es1 ~] # cat / etc/security/limits.d/20-nproc.conf * soft nproc 40960 * hard nproc 40960 [3]: max virtual memory areas vm.max_map_count [65530] is too low Increase to at least [262144] [root@es1 ~] # cat / etc/sysctl.conf vm.max_map_count= 655360 [root @ es1 ~] # sysctl-pvm.max_map_count = 655360 [root@es1 ~] # "detailed installation process of Elasticsearch7.2 Cluster" ends here 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.
Views: 0
*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.
Continue with the installation of the previous hadoop.First, install zookooper1. Decompress zookoope
"Every 5-10 years, there's a rare product, a really special, very unusual product that's the most un
© 2024 shulou.com SLNews company. All rights reserved.