In addition to Weibo, there is also WeChat
Please pay attention
WeChat public account
Shulou
2025-04-02 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Development >
Share
Shulou(Shulou.com)05/31 Report--
Most people do not understand the knowledge of this article "Windows10 how to build ElasticSearch cluster service", so the editor summarizes the following content, detailed content, clear steps, and has a certain reference value. I hope you can get something after reading this article. Let's take a look at this "how to build ElasticSearch cluster service in Windows10" article.
Copy a file
Image.png
Change the profile elasticsearch.yml of elasticsearch
# set the cluster name. The names of all nodes in the cluster must be the same. Cluster.name: my-esCluster# sets the node name. The node name in the cluster must be unique. Node.name: node1# indicates whether the node will be the master node, and true indicates that it will. False means no node.master: whether the current node of true# can be used to store data, yes: true, No: falsenode.data: location where true# index data is stored # path.data: / opt/elasticsearch/data# log file storage location # path.logs: / opt/elasticsearch/logs# needs to lock physical memory, yes: true, No: false#bootstrap.memory_lock: true# listening address It is used to access the http port provided by the esnetwork.host: 192.168.0.11 es. The default listening port is 9200http.port: 920 TCP, and the default 9300transport.tcp.port: 930 port is set to ensure that the nodes in the cluster can know about the other N master qualified nodes. Default is 1. For large clusters, you can set a larger value (2-4) discovery.zen.minimum_master_nodes: write the facility address of the candidate primary node to the newly added configuration after "es7.x". Discovery.seed_hosts can be selected as the master node after the service is enabled: ["192.168.0.1141mdiscovery.zen.fd.ping_retries 9300", "192.168.0.1141mdiscovery.zen.fd.ping_retries 9301", "192.168.0.1141mdiscovery.zen.fd.ping_retries 9302"] configuration added after enabling es7.x This configuration is required to initialize a new cluster to elect mastercluster.initial_master_nodes: ["node1", "node2", "node3"] # whether cross-domain support is: true This configuration is required when using the head plug-in http.cors.enabled: true# "*" means that all domain names are supported: "*" action.destructive_requires_name: trueaction.auto_create_index: .security, .domains *, .configured _ watches,.watcher-history*xpack.security.enabled: falsexpack.monitoring.enabled: truexpack.graph.enabled: falsexpack.watcher.enabled: falsexpack.ml.enabled: false# sets the cluster name The names of all nodes in the cluster must be the same. Cluster.name: my-esCluster# sets the node name. The node name in the cluster must be unique. Node.name: node2# indicates whether the node will be the master node, and true indicates that it will. False means no node.master: whether the current node of true# can be used to store data, yes: true, No: falsenode.data: location where true# index data is stored # path.data: / opt/elasticsearch/data# log file storage location # path.logs: / opt/elasticsearch/logs# needs to lock physical memory, yes: true, No: false#bootstrap.memory_lock: true# listening address It is used to access the http port provided by the esnetwork.host: 192.168.0.11 es. The default listening port is 9200http.port: 920 TCP, and the default 9300transport.tcp.port: 930 port is set to ensure that the nodes in the cluster can know about the other N master qualified nodes. Default is 1. For large clusters, you can set a larger value (2-4) discovery.zen.minimum_master_nodes: write the facility address of the candidate primary node to the newly added configuration after "es7.x". Discovery.seed_hosts can be selected as the master node after the service is enabled: ["192.168.0.1141mdiscovery.zen.fd.ping_retries 9300", "192.168.0.1141mdiscovery.zen.fd.ping_retries 9301", "192.168.0.1141mdiscovery.zen.fd.ping_retries 9302"] configuration added after enabling es7.x This configuration is required to initialize a new cluster to elect mastercluster.initial_master_nodes: ["node1", "node2", "node3"] # whether cross-domain support is: true This configuration is required when using the head plug-in http.cors.enabled: true# "*" means that all domain names are supported: "*" action.destructive_requires_name: trueaction.auto_create_index: .security, .domains *, .configured _ watches,.watcher-history*xpack.security.enabled: falsexpack.monitoring.enabled: truexpack.graph.enabled: falsexpack.watcher.enabled: falsexpack.ml.enabled: false# sets the cluster name The names of all nodes in the cluster must be the same. Cluster.name: my-esCluster# sets the node name. The node name in the cluster must be unique. Node.name: node3# indicates whether the node will be the master node, and true indicates that it will. False means no node.master: whether the current node of true# can be used to store data, yes: true, No: falsenode.data: location where true# index data is stored # path.data: / opt/elasticsearch/data# log file storage location # path.logs: / opt/elasticsearch/logs# needs to lock physical memory, yes: true, No: false#bootstrap.memory_lock: true# listening address It is used to access the http port provided by the esnetwork.host: 192.168.0.11 es. The default listening port is 9200http.port: 920 TCP, and the default 9300transport.tcp.port: 930 port is set to ensure that the nodes in the cluster can know about the other N master qualified nodes. Default is 1. For large clusters, you can set a larger value (2-4) discovery.zen.minimum_master_nodes: write the facility address of the candidate primary node to the newly added configuration after "es7.x". Discovery.seed_hosts can be selected as the master node after the service is enabled: ["192.168.0.1141mdiscovery.zen.fd.ping_retries 9300", "192.168.0.1141mdiscovery.zen.fd.ping_retries 9301", "192.168.0.1141mdiscovery.zen.fd.ping_retries 9302"] configuration added after enabling es7.x This configuration is required to initialize a new cluster to elect mastercluster.initial_master_nodes: ["node1", "node2", "node3"] # whether cross-domain support is: true This configuration is required when using the head plug-in http.cors.enabled: true# "*" means all domain names are supported: http.cors.allow-origin: "*" action.destructive_requires_name: trueaction.auto_create_index: .security, .domains *, .powered _ watches,.watcher-history*xpack.security.enabled: falsexpack.monitoring.enabled: truexpack.graph.enabled: falsexpack.watcher.enabled: falsexpack.ml.enabled: false
If the above method starts the three nodes in turn, you can see the success of the three nodes after the startup is completed.
The above is the content of this article on "how to build ElasticSearch Cluster Service in Windows10". I believe we all have a certain understanding. I hope the content shared by the editor will be helpful to you. If you want to know more about the relevant knowledge, please 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.
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.