Elasticsearch: discovery-ec2 plugin not working in elasticsearch 7.0.0

[vivekgkwd]

discovery ec2 plugin is not able to discover master in 7.0.0
It was working fine before upgrading the cluster, I removed and reinstalled the plugin. Also created a fresh setup.

Am getting the following error :

[vivekgkwd]

Logs on master :

[vivekgkwd]

initial master nodes :(

[wedneyyuri]

How did you solve this problem? There's any other way than forcing a list of IPs or dns?

[Giaco9]

I have the same problem, how did you solve it?

[wedneyyuri]

Starting an Elasticsearch cluster for the very first time requires the initial set of master-eligible nodes to be explicitly defined on one or more of the master-eligible nodes in the cluster.

In other words, I see two options here:

• explicitly define the "initial_master_nodes" (elasticsearch.yml) on every master-eligible nodes in the cluster
• setup all instances, then log in one master eligible node and start it as a single node (discovery.type=single-node), remove the discovery type config and let them know each other.

[LloydArmstrong]

• explicitly define the "initial_master_nodes" (elasticsearch.yml) on every master-eligible nodes in the cluster

This did not work. When adding this to elasticsearch.yml, Elasticsearch fails to start stating:

java.lang.IllegalArgumentException: unknown setting [initial_master_nodes] please check that any required plugins are installed, or check the breaking changes documentation for removed settings

[wedneyyuri]

@LloydArmstrong The configuration is cluster.initial_master_nodes, not initial_master_nodes.

https://www.elastic.co/guide/en/elasticsearch/reference/master/discovery-settings.html#initial_master_nodes

[klimchuk]

How to disable bootstrapping in production? We have other means to have 3 master nodes (via discovery.ec2.tag.*) and 7.x bootstrapping has no benefits to us.

[kuni255]

I have same problem in Ver. 7.3. So I also would like to know how @vivekgkwd solved this issue.