Nodes discovery after upgrading from 1.7.1 to 2.2.0


#1

I have upgraded from 1.7.1 to 2.2.0 and the nodes cannot form a cluster
I have successfully installed cloud-aws plugin
Here is elasticsearch.yml configuration

path.data: /var/data/elasticsearch
cluster.name: Mycompanyname-QA
node.master: true
node.name: ElasticSearch-QA-01
http.cors.enabled: true
plugin.mandatory: cloud-aws
bootstrap.mlockall: true
cloud.aws.access_key: XXXXXXXXXX
cloud.aws.secret_key: XXXXXXXXXXXXX
discovery.type: ec2
discovery.zen.ping.multicast.enabled: false
discovery.ec2.groups: SECURITY-GROUP-Logs-VPC
discovery.zen.minimum_master_nodes: 1

I also noticed when Elasticsearch 2.2 started it publishes the loopback IP address not the hostname IP

publish_address {127.0.0.1:9300}, bound_addresses {127.0.0.1:9300}

Please help


(mv) #2

+1 please help same issue here


(Mike Simos) #3

Hi,

Add network.host: 0.0.0.0 to your elasticsearch.yml. This will bind to all interfaces. By default Elasticsearch 2.x only binds to localhost unless you specify something else:

https://www.elastic.co/guide/en/elasticsearch/reference/current/breaking_20_network_changes.html#breaking_20_network_changes


#4

Thanks for the quick feedback Mike, a follow-up question regarding network.host: 0.0.0.0
We have 3 clusters in DEV, QA and Prod, is there a possibility that a node in DEV cluster joins the QA or Prod cluster?


(Mike Simos) #5

Hi,

Only if you're using multicast and the same cluster name for all 3 clusters.


#6

We don't
Thank you it works


(Mark Walkom) #7

This issue is why there is a stickied thread at the top :wink:


(system) #8