# The nodes are not coming as part of cluster

**URL:** <https://discuss.elastic.co/t/the-nodes-are-not-coming-as-part-of-cluster/200747>\
**Category:** Elasticsearch\
**Created:** [September 23, 2019, 8:14pm UTC](https://discuss.elastic.co/t/the-nodes-are-not-coming-as-part-of-cluster/200747 "2019-09-23T20:14:10Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![elasticized](https://avatars.discourse-cdn.com/v4/letter/e/df705f/32.png) [@elasticized](https://discuss.elastic.co/u/elasticized)\
**Post date:** [September 23, 2019, 8:14pm UTC](https://discuss.elastic.co/t/the-nodes-are-not-coming-as-part-of-cluster/200747/1 "2019-09-23T20:14:10Z")

</div>

I have upgraded my ES to 7.3.2, and I have the correct elasticsearch.yml files.  
The 2 nodes are on EC2 and both master and data. Following are elasticsearch.yml for node -1 and node-2 respectively:

Node1:

cluster.name: cluster  
node.master: true  
node.data: true  
node.ingest: true  
path.data: /app/data/lib/elasticsearch  
path.logs: /app/log/elasticsearch  
network.host: 10.250.60.22  
http.port: 9200  
discovery.seed\_hosts: ["10.250.60.22","10.250.70.232"]  
cluster.initial\_master\_nodes: ["10.250.60.22","10.250.70.232"]  
logger.org.elasticsearch.discovery: TRACE

Node 2:  
cluster.name: cluster  
node.master: true  
node.data: true  
node.ingest: true  
path.data: /app/data/lib/elasticsearch  
path.logs: /app/log/elasticsearch  
network.host: 10.250.70.232  
http.port: 9200  
discovery.seed\_hosts: ["10.250.60.22","10.250.70.232"]  
cluster.initial\_master\_nodes: ["10.250.60.22","10.250.70.232"]  
logger.org.elasticsearch.discovery: TRACE

As you can see, I enabled TRACE settings and see the following in server: 10.250.60.22

[2019-09-23T18:31:48,642][TRACE][o.e.d.SeedHostsResolver] [ip-10-250-60-22] resolved host [10.250.60.22] to [10.250.60.22:9300]  
[2019-09-23T18:31:48,643][TRACE][o.e.d.SeedHostsResolver] [ip-10-250-60-22] resolved host [10.250.70.232] to [10.250.70.232:9300]  
[2019-09-23T18:31:48,644][TRACE][o.e.d.PeerFinder] [ip-10-250-60-22] probing resolved transport addresses [10.250.70.232:9300]

So communication and network is not an issue.

Also, when I change the other node to be just data, and not master, the cluster shows 2 nodes.  
But it seems unstable.

Any suggestions, as I am inclined to think this is an ES 7.3.2 issue.

---

<div class="post-metadata">

**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\
**Post date:** [September 24, 2019, 8:46am UTC](https://discuss.elastic.co/t/the-nodes-are-not-coming-as-part-of-cluster/200747/2 "2019-09-24T08:46:26Z")

</div>

can you share more log files? showing master node elections and pinging other nodes?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [October 22, 2019, 8:46am UTC](https://discuss.elastic.co/t/the-nodes-are-not-coming-as-part-of-cluster/200747/3 "2019-10-22T08:46:30Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.