# Client Node cannot be discovered by Master
**URL:** https://discuss.elastic.co/t/client-node-cannot-be-discovered-by-master/49947
**Category:** Elasticsearch
**Created:** [May 12, 2016, 10:37pm UTC](https://discuss.elastic.co/t/client-node-cannot-be-discovered-by-master/49947 "2016-05-12T22:37:16Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@sharon.c](https://discuss.elastic.co/u/sharon.c)
#### Post date: [May 12, 2016, 10:37pm UTC](https://discuss.elastic.co/t/client-node-cannot-be-discovered-by-master/49947/1 "2016-05-12T22:37:16Z")
We set up a 3 nodes elasticsearch cluster, 1 Master (data) node, 1 data node, and 1 client node.
Client node elasticsearch.yml file
>
cluster.name: elkstats
node.name: clientnode
node.master: false
node.data: false
path.data: /data
network.bind\_host: 10.100.16.9
network.publish\_host: 10.100.16.9
http.port: 9200
http.cors.enabled: true
http.cors.allow-origin: "\*"
Master node elasticsearch.yml file
>
cluster.name: elkstats
node.name: Melasticsearch
node.master: true
node.data: true
discovery.zen.ping.multicast.enabled: false
discovery.zen.ping.unicast.hosts: ["Melasticsearch","datanode1","clientnode"]
path.data: /data
network.bind\_host: 10.100.16.13
network.publish\_host: 10.100.16.13
http.cors.enabled: true
http.cors.allow-origin: "\*"
http.port: 9200
Data node elasticsearch.yml file
>
cluster.name: elkstats
node.name: datanode1
node.master: false
node.data: true
path.data: /data
network.bind\_host: 10.100.16.11
network.publish\_host: 10.100.16.11
http.port: 9200
http.cors.enabled: true
http.cors.allow-origin: "\*"
When I am on client node, I can do
curl -XGET clientnode:9200
it shows elasticsearch is running on client
>
{
"name" : "clientnode",
"cluster\_name" : "elkstats",
"version" : {
"number" : "2.3.1",
"build\_hash" : "bd980929010aef404e7cb0843e61d0665269fc39",
"build\_timestamp" : "2016-04-04T12:25:05Z",
"build\_snapshot" : false,
"lucene\_version" : "5.5.0"
}
}
I set the following in the /etc/hosts file for all the nodes
>
10.100.16.13 Melasticsearch
10.100.16.11 datanode1
10.100.16.9 clientnode
When I am on any of the node, I use
curl -XGET '[http://Melasticsearch:9200/\_cluster/health?pretty=true](http://Melasticsearch:9200/_cluster/health?pretty=true)'
It shows there are only two nodes
>
{
"cluster\_name" : "elkstats",
"status" : "green",
"timed\_out" : false,
"number\_of\_nodes" : 2,
"number\_of\_data\_nodes" : 2,
"active\_primary\_shards" : 11,
"active\_shards" : 19,
"relocating\_shards" : 0,
"initializing\_shards" : 0,
"unassigned\_shards" : 0,
"delayed\_unassigned\_shards" : 0,
"number\_of\_pending\_tasks" : 0,
"number\_of\_in\_flight\_fetch" : 0,
"task\_max\_waiting\_in\_queue\_millis" : 0,
"active\_shards\_percent\_as\_number" : 100.0
}
When I am on other nodes, and do curl to client
curl -XGET clientnode:9200
The response shows:
>
curl: (7) Failed connect to clientnode:9200; Connection refused
It looks like client node is not broadcasting its service to other nodes, and the other nodes are not aware of client node.
How do I make the client node join the cluster and recognized by the other nodes?
---
### Author:  [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [May 12, 2016, 11:52pm UTC](https://discuss.elastic.co/t/client-node-cannot-be-discovered-by-master/49947/2 "2016-05-12T23:52:02Z")
You haven't set the unicast list - [https://www.elastic.co/guide/en/elasticsearch/guide/master/important-configuration-changes.html#unicast](https://www.elastic.co/guide/en/elasticsearch/guide/master/important-configuration-changes.html#unicast)
---
### Author:  [@sharon.c](https://discuss.elastic.co/u/sharon.c)
#### Post date: [May 13, 2016, 12:09am UTC](https://discuss.elastic.co/t/client-node-cannot-be-discovered-by-master/49947/3 "2016-05-13T00:09:17Z")
When I added this line in the clientnode elasticsearch.yml file and restarted elasticsearch, it works
>
discovery.zen.ping.unicast.hosts: ["Melasticsearch"]
Thank you for the answer
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 5, 2017, 10:51pm UTC](https://discuss.elastic.co/t/client-node-cannot-be-discovered-by-master/49947/4 "2017-07-05T22:51:36Z")