# Elasticsearch MultiNode Cluster Configuration **URL:** \ **Category:** Elasticsearch\ **Created:** [February 21, 2018, 3:56pm UTC](https://discuss.elastic.co/t/elasticsearch-multinode-cluster-configuration/120883 "2018-02-21T15:56:08Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![Hassan\_Shaitou](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hassan_shaitou/32/103867_2.png) [@Hassan\_Shaitou](https://discuss.elastic.co/u/Hassan_Shaitou)\ **Post date:** [February 21, 2018, 3:56pm UTC](https://discuss.elastic.co/t/elasticsearch-multinode-cluster-configuration/120883/1 "2018-02-21T15:56:08Z")
I have two nodes I want one to act as a master(master node) the second to act as a slave(data node): master node configuration: ``` cluster.name: twist node.master: true node.data: false node.name: 192.168.237.131 discovery.zen.ping.unicast.hosts: ["192.168.237.131","192.168.237.132"] ``` data node configuration: ``` cluster.name: twist node.master: false node.data: true node.name: 192.168.237.132 discovery.zen.ping.unicast.hosts: ["192.168.237.131","192.168.237.132"] ``` but, the problem I am getting the following warning > [2018-02-21T07:53:52,506][WARN][o.e.d.z.ZenDiscovery] [192.168.237.131] not enough master nodes discovered during pinging (found [], but needed [-1]), pinging again in addition I checked the cluster on the master node by running the following command line: ``` curl http://192.168.237.131:9200/_cluster/health?pretty ``` I only get one master node which is my machine, and 0 data nodes ! I am using ES version 6.0.0 any configuration missing ? Thanks in adnvance... ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [February 21, 2018, 4:24pm UTC](https://discuss.elastic.co/t/elasticsearch-multinode-cluster-configuration/120883/2 "2018-02-21T16:24:17Z")
Just to make sure you understand, I'd like to highlight that there is no such master/slave mechanism in elasticsearch. We do have master elligible nodes that can control the cluster state. We do have data nodes that can have indices allocated on them (data on disk). And nodes can do both. In the context of a 2 nodes cluster, that does not sound a good idea to dedicate nodes to do master and the other to do only data. Anyway, the problem here is that you did not set `network.host` I think. Another comment: you need 3 nodes to be safer for production. My advice would be to have at least: - 2 data/master nodes - 1 master only node (which can be much lighter in term of memory and can use spinning disk) ---
**Author:** ![Hassan\_Shaitou](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hassan_shaitou/32/103867_2.png) [@Hassan\_Shaitou](https://discuss.elastic.co/u/Hassan_Shaitou)\ **Post date:** [February 21, 2018, 4:27pm UTC](https://discuss.elastic.co/t/elasticsearch-multinode-cluster-configuration/120883/3 "2018-02-21T16:27:22Z")
I will check `network.host`, yah I read about it that a node can do both roles as master and data I meant by slave node the nodes who do the data part. Thanks for replying and clarifying things. ---
**Author:** ![Hassan\_Shaitou](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hassan_shaitou/32/103867_2.png) [@Hassan\_Shaitou](https://discuss.elastic.co/u/Hassan_Shaitou)\ **Post date:** [February 22, 2018, 7:40am UTC](https://discuss.elastic.co/t/elasticsearch-multinode-cluster-configuration/120883/4 "2018-02-22T07:40:19Z")
sorry for bothering,I changed my settings on Master/Data machine(1-2) (I made both machines as Master/Data Nodes) My updated configuration: > ``` > http.port: 9200 > http.host: 0.0.0.0 > node.master: true > node.data: true > node.ingest: false > network.host: 127.0.0.1 > transport.host: 192.168.237.132 > node.name: 192.168.237.132 > discovery.zen.ping.unicast.hosts: ["192.168.237.131","192.168.237.132"] > > ``` But I am still getting this error: > [2018-02-21T23:37:47,039][INFO][o.e.b.BootstrapChecks] [192.168.237.132] bound or publishing to a non-loopback or non-link-local address, enforcing bootstrap checks > ERROR: [2] bootstrap checks failed ---
**Author:** ![Hassan\_Shaitou](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hassan_shaitou/32/103867_2.png) [@Hassan\_Shaitou](https://discuss.elastic.co/u/Hassan_Shaitou)\ **Post date:** [February 22, 2018, 7:58am UTC](https://discuss.elastic.co/t/elasticsearch-multinode-cluster-configuration/120883/5 "2018-02-22T07:58:21Z")
Sorry for bothering again, the IP 192.168.237.132 is not resolved in the /etc/hosts I replaced it by "localhost" and the elastic is now running, but still the nodes are not connected ! Am I still missing a configuration option? ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [February 22, 2018, 8:11am UTC](https://discuss.elastic.co/t/elasticsearch-multinode-cluster-configuration/120883/6 "2018-02-22T08:11:01Z")
Please read [https://www.elastic.co/guide/en/elasticsearch/reference/current/bootstrap-checks.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/bootstrap-checks.html) ---
**Author:** ![Hassan\_Shaitou](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hassan_shaitou/32/103867_2.png) [@Hassan\_Shaitou](https://discuss.elastic.co/u/Hassan_Shaitou)\ **Post date:** [February 22, 2018, 8:13am UTC](https://discuss.elastic.co/t/elasticsearch-multinode-cluster-configuration/120883/7 "2018-02-22T08:13:02Z")
thanks thanks I read it, it worked now, by the way it's not the issue thanks anyways, I just added my machine IP to the /etc/hosts and it is working like charm. Thanks again... ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [March 22, 2018, 8:13am UTC](https://discuss.elastic.co/t/elasticsearch-multinode-cluster-configuration/120883/8 "2018-03-22T08:13:04Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.