Elasticsearch master slave configuration

Elastic Stack Elasticsearch
1

Hi,
I'm trying to configuration a cluster with 1 Master node , 2 slave nodes. After restarting the service, master elascticseach.bat is okey but slave elascticseach.bat been getting the following error:
[node_154] not enough master nodes discovered during pinging (found [[]], but needed [-1]), pinging again

Master elasticsearch.yml configuration ip:10.200.2.152

cluster.name: project_cluster
node.name: mlpcare_node_152
node.master: true
node.data: true
node.ingest: false
bootstrap.memory_lock: true
discovery.zen.ping.unicast.hosts: ["ES152","ES153", "ES154"]

slave node config

cluster.name: project_cluster ip:10.200.2.153
node.name: node_153
node.master: false
node.data: true
node.ingest: false
network.host: 0.0.0.0
discovery.zen.ping.unicast.hosts: ["ES152","ES153", "ES154"]

cluster.name: project_cluster ip:10.200.2.154
node.name: node_154
node.master: false
node.data: true
node.ingest: false
network.host: 0.0.0.0
discovery.zen.ping.unicast.hosts: ["ES152","ES153", "ES154"]

hosts Same
#127.0.0.1 localhost
10.200.2.152 ES152
10.200.2.153 ES153
10.200.2.154 ES154

2

Elasticsearch is designed to run clustered, not in a master-slave setup. You should therefore make all your nodes master eligible and set minimum_master_nodes to 2 as perthese guidelines. Running with a single master-eligible node is bad and makes that a single point of failure.

Also verify that all host can connect to port 9300 on the other hosts and that no firewall rules are preventing this.

3

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.