I'm trying to configure Elastic Search on one of our remote servers. I've installed it with .msi setup file (v7.1.1) and configured the firewall for 9200 and 9300 ports.
When I set network.publish_host to server ip it gave me this error the default discovery settings are unsuitable for production use; at least one of [discovery.seed_hosts, discovery.seed_providers, cluster.initial_master_nodes] must be configured. Then I've made some research and set cluster.initial_master_nodes to my single node which named "ElasticSearchNode". Now the service is running but when i check the cluster health it says "master_not_discovered_exception".
Struggled with cluster connection problems somewhat as well. Below are the relevant pieces of my yml file.
I believe one of the mistakes may be that you do not have node.master in your yml file.
In this, servername1 and servername2 should be replaced by the correct dns name of your servers.
Note that you will need to edit the yml files of all your nodes in the cluster.
As a general rule for a 2 node cluster, set both node up as data and master node.
Hi and thanks for help. Actually I have only one server for elasticsearch. I've changed my yml file according to your suggestion but I'm still getting the same warning which says:
[2019-07-04T10:57:36,163][WARN ][o.e.c.c.ClusterFormationFailureHelper] [ElasticNode1] master not discovered or elected yet, an election requires a node with id [Q7UjKuM3QimcL4pCKmUB6w], have discovered [] which is not a quorum; discovery will continue using [] from hosts providers and [{ElasticNode1}{S1tdE5hQTCeXwElJUyqBXw}{zvSpL_10ThCs9VWcwFJc0w}{x.x.x.x}{x.x.x.x:9300}{ml.machine_memory=17179398144, xpack.installed=true, ml.max_open_jobs=20}] from last-known cluster state; node term 1, last-accepted version 14 in term 1
Hello,
Do you have a specific reason to create a cluster when you only have 1 node?
I never tried a single node cluster to be honest.
Other than that, could you give it a try to have the same setting for network.host and network.bind-host and make sure it is the same as the seed_hosts.
Sometimes it also makes sense to clean out the data directory. I has happened to me that some cluster info in there was not correct after changing the cluster config, and cleaning the data dir re-executes the registrations and that has helped me on at least 1 occasion.
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.