# ConnectTransportException non-master-eligible node found
**URL:** https://discuss.elastic.co/t/connecttransportexception-non-master-eligible-node-found/266417
**Category:** Elasticsearch
**Created:** [March 6, 2021, 1:01am UTC](https://discuss.elastic.co/t/connecttransportexception-non-master-eligible-node-found/266417 "2021-03-06T01:01:51Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@SSRR](https://discuss.elastic.co/u/SSRR)
#### Post date: [March 6, 2021, 1:01am UTC](https://discuss.elastic.co/t/connecttransportexception-non-master-eligible-node-found/266417/1 "2021-03-06T01:01:51Z")
I'm configuring Elasticserach 7.9.0 cluster with 2 hosts. The elasticsearch.yml in host1 is setup with node.master as true and host2 is setup with node.master as false.
Both hosts have elasticsearch started but with error in host2. Each node is up and running but they are not communicating with each other. Enabled trace for discovery.
Host1 logs indicate: [2021-03-05T18:49:39,125][TRACE][o.e.d.PeerFinder] [liferaydev1] probing resolved transport addresses [192.168.253.19:9300]
[2021-03-05T18:49:39,125][TRACE][o.e.d.PeerFinder] [liferaydev1] Peer{transportAddress=192.168.253.19:9300, discoveryNode=null, peersRequestInFlight=false} attempting connection
[2021-03-05T18:49:39,125][TRACE][o.e.d.HandshakingTransportAddressConnector] [liferaydev1] [connectToRemoteMasterNode[192.168.253.19:9300]] opening probe connection
[2021-03-05T18:49:39,127][TRACE][o.e.d.HandshakingTransportAddressConnector] [liferaydev1] [connectToRemoteMasterNode[192.168.253.19:9300]] opened probe connection
[2021-03-05T18:49:39,128][TRACE][o.e.d.HandshakingTransportAddressConnector] [liferaydev1] [connectToRemoteMasterNode[192.168.253.19:9300]] handshake successful: {liferaydev2}{mOHlwT5kTXWcYD5QWCkkQQ}{w1\_LFj-cTZWa5IuJTAE2rA}{liferaydev2}{192.168.253.19:9300}{dilrt}{ml.machine\_memory=13640597504, ml.max\_open\_jobs=20, xpack.installed=true, transform.node=true}
[2021-03-05T18:49:39,128][DEBUG][o.e.d.PeerFinder] [liferaydev1] Peer{transportAddress=192.168.253.19:9300, discoveryNode=null, peersRequestInFlight=false} connection failed
org.elasticsearch.transport.ConnectTransportException: [liferaydev2][192.168.253.19:9300] non-master-eligible node found
Elasticsearch in host1
cluster.name: liferay-elastic-cluster
node.name: liferaydev1
network.publish\_host: liferaydev1
network.host: 192.168.253.18
network.bind\_host: liferaydev1
http.port: 9200
transport.tcp.port: 9300
discovery.zen.ping.unicast.hosts: ["192.168.253.18:9300", "192.168.253.19:9300"]
cluster.initial\_master\_nodes: ["liferaydev1", "liferaydev2"]
discovery.zen.minimum\_master\_nodes: 2
node.master: true
logger.org.elasticsearch.discovery: TRACE
Elasticsearch in host2
node.name: liferaydev2
network.publish\_host: liferaydev2
network.host: 192.168.253.19
network.bind\_host: liferaydev2
http.port: 9200
discovery.zen.ping.unicast.hosts: ["192.168.253.18:9300", "192.168.253.19:9300"]
cluster.initial\_master\_nodes: ["liferaydev1", "liferaydev2"]
discovery.zen.minimum\_master\_nodes: 2
node.master: false
What is missing in the host1 configuration....please help.
Thank you.
---
### Author:  [@nugusbayevkk](https://discuss.elastic.co/u/nugusbayevkk)
#### Post date: [March 6, 2021, 1:24pm UTC](https://discuss.elastic.co/t/connecttransportexception-non-master-eligible-node-found/266417/2 "2021-03-06T13:24:33Z")
Hi @SSRR
There are some changes in discovery configuration:
1. Look at [Discovery | Elasticsearch Reference [7.9] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/7.9/modules-discovery-hosts-providers.html#settings-based-hosts-provider)
```auto
node1:
discovery.seed_hosts: ["ip2:9300"]
node2:
discovery.seed_hosts: ["ip1:9300"]
```
1. [Node | Elasticsearch Reference [7.9] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/7.9/modules-node.html#voting-only-node)
`node.master` configuration I think is deprecated according to documentation, instead of use
`node.roles: [master,data] or node.roles: [data]`
2. `discovery.zen.minimum_master_nodes: 2` this configuration is deprecated, look at : [Breaking changes in 7.0 | Elasticsearch Reference [7.9] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/7.9/breaking-changes-7.0.html#_cluster_bootstrapping_is_required_if_discovery_is_configured)
instead of use `cluster.initial_master_nodes: ["liferaydev1", "liferaydev2"]`
**Note** If you want that NODE1 - master only, you should in cluster.inital\_master\_nodes set only `"liferaydev1"` value.
---
### Author:  [@SSRR](https://discuss.elastic.co/u/SSRR)
#### Post date: [March 10, 2021, 4:00pm UTC](https://discuss.elastic.co/t/connecttransportexception-non-master-eligible-node-found/266417/3 "2021-03-10T16:00:28Z")
Thank you so much for the suggestions.
I changed to
'cluster.initial\_master\_nodes: ["node1\_name"]'
Kept these same, though deprecated in Elasticsearch 7.9:
1. 'node.master=' same as before in node1 and node2.
2. 'discovery.zen.minimum\_master\_nodes: 2' same as before in node1 and node2
and it worked.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [April 7, 2021, 4:00pm UTC](https://discuss.elastic.co/t/connecttransportexception-non-master-eligible-node-found/266417/4 "2021-04-07T16:00:33Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.