# Nodes discovery after upgrading from 1.7.1 to 2.2.0 **URL:** \ **Category:** Elasticsearch\ **Created:** [February 17, 2016, 6:23pm UTC](https://discuss.elastic.co/t/nodes-discovery-after-upgrading-from-1-7-1-to-2-2-0/42061 "2016-02-17T18:23:40Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![genesis](https://avatars.discourse-cdn.com/v4/letter/g/96bed5/32.png) [@genesis](https://discuss.elastic.co/u/genesis)\ **Post date:** [February 17, 2016, 6:23pm UTC](https://discuss.elastic.co/t/nodes-discovery-after-upgrading-from-1-7-1-to-2-2-0/42061/1 "2016-02-17T18:23:40Z")
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](http://cluster.name): Mycompanyname-QA node.master: true [node.name](http://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 ---
**Author:** ![Madhuri\_Vemuri](https://avatars.discourse-cdn.com/v4/letter/m/a87d85/32.png) [@Madhuri\_Vemuri](https://discuss.elastic.co/u/Madhuri_Vemuri)\ **Post date:** [February 17, 2016, 7:12pm UTC](https://discuss.elastic.co/t/nodes-discovery-after-upgrading-from-1-7-1-to-2-2-0/42061/2 "2016-02-17T19:12:43Z")
+1 please help same issue here ---
**Author:** ![msimos](https://avatars.discourse-cdn.com/v4/letter/m/bb73d2/32.png) [@msimos](https://discuss.elastic.co/u/msimos)\ **Post date:** [February 17, 2016, 7:26pm UTC](https://discuss.elastic.co/t/nodes-discovery-after-upgrading-from-1-7-1-to-2-2-0/42061/3 "2016-02-17T19:26:34Z")
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](https://www.elastic.co/guide/en/elasticsearch/reference/current/breaking_20_network_changes.html#breaking_20_network_changes) ---
**Author:** ![genesis](https://avatars.discourse-cdn.com/v4/letter/g/96bed5/32.png) [@genesis](https://discuss.elastic.co/u/genesis)\ **Post date:** [February 17, 2016, 8:14pm UTC](https://discuss.elastic.co/t/nodes-discovery-after-upgrading-from-1-7-1-to-2-2-0/42061/4 "2016-02-17T20:14:56Z")
> [@msimos](#): > > [https://www.elastic.co/guide/en/elasticsearch/reference/current/breaking\_20\_network\_changes.html#breaking\_20\_network\_changes](https://www.elastic.co/guide/en/elasticsearch/reference/current/breaking_20_network_changes.html#breaking_20_network_changes) 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? ---
**Author:** ![msimos](https://avatars.discourse-cdn.com/v4/letter/m/bb73d2/32.png) [@msimos](https://discuss.elastic.co/u/msimos)\ **Post date:** [February 17, 2016, 8:28pm UTC](https://discuss.elastic.co/t/nodes-discovery-after-upgrading-from-1-7-1-to-2-2-0/42061/5 "2016-02-17T20:28:10Z")
Hi, Only if you're using multicast and the same cluster name for all 3 clusters. ---
**Author:** ![genesis](https://avatars.discourse-cdn.com/v4/letter/g/96bed5/32.png) [@genesis](https://discuss.elastic.co/u/genesis)\ **Post date:** [February 17, 2016, 8:29pm UTC](https://discuss.elastic.co/t/nodes-discovery-after-upgrading-from-1-7-1-to-2-2-0/42061/6 "2016-02-17T20:29:55Z")
We don't Thank you it works ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [February 17, 2016, 9:23pm UTC](https://discuss.elastic.co/t/nodes-discovery-after-upgrading-from-1-7-1-to-2-2-0/42061/7 "2016-02-17T21:23:01Z")
This issue is why there is a stickied thread at the top 😉 > [@Connectivity issues with a new/upgraded 2.X cluster? Read here first slight\_smile](https://discuss.elastic.co/t/connectivity-issues-with-a-new-upgraded-2-x-cluster-read-here-first/35699/7): > > Well it's connecting to a valid interface. I'd suggest you create a separate thread and ask, I don't think this is a settings issue related to the original post. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 5, 2017, 11:15pm UTC](https://discuss.elastic.co/t/nodes-discovery-after-upgrading-from-1-7-1-to-2-2-0/42061/8 "2017-07-05T23:15:34Z")