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:
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)
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.
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?
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...
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.