Hi all,
I have 2 EC2 Windows instances running with Elasticsearch 5.5.1 and I want to connect them into a cluster, but I'm having trouble having them find eachother. Here are their YMLs:
Their IPs are set to the assigned private EC2 IP addresses. I have tried using public IPs as well.
AWS security groups for the instances have been set up to include IPs from anywhere. Their respective IPs return responses when pinged.
I have also tried the EC2 discovery plugin. Both have that plugin installed and are included in an AWS group policy that corresponds to my AWS credentials. The YML looks like this:
[2017-08-07T14:14:18,059][INFO ][o.e.n.Node ] [nodeA] node name [nodeA], node ID [0gppTofrQNaJpMDn84kQRw]
....
[2017-08-07T14:14:24,609][INFO ][o.e.d.DiscoveryModule ] [nodeA] using discovery type [zen]
[2017-08-07T14:14:25,239][INFO ][o.e.n.Node ] [nodeA] initialized
[2017-08-07T14:14:25,240][INFO ][o.e.n.Node ] [nodeA] starting ...
[2017-08-07T14:14:25,556][INFO ][o.e.t.TransportService ] [nodeA] publish_address {ip1:9300}, bound_addresses {ip1:9300}
[2017-08-07T14:14:25,569][INFO ][o.e.b.BootstrapChecks ] [nodeA] bound or publishing to a non-loopback or non-link-local address, enforcing bootstrap checks
[2017-08-07T14:14:28,635][INFO ][o.e.c.s.ClusterService ] [nodeA] new_master {nodeA}{0gppTofrQNaJpMDn84kQRw}{f_mVXakOToSNZ6FaAAGx3w}{ip1}{ip1:9300}, reason: zen-disco-elected-as-master ([0] nodes joined)
[2017-08-07T14:14:28,664][INFO ][o.e.h.n.Netty4HttpServerTransport] [nodeA] publish_address {ip1:9200}, bound_addresses {ip1:9200}
[2017-08-07T14:14:28,665][INFO ][o.e.n.Node ] [nodeA] started
Both logs are like this, with different node names and ips obviously. Also checked both VPC and subnet, they are all the same for the instances. They can ping eachother's private IP.
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.