# ES 2.3.3 node cannot join the master node

**URL:** <https://discuss.elastic.co/t/es-2-3-3-node-cannot-join-the-master-node/55061>\
**Category:** Elasticsearch\
**Created:** [July 8, 2016, 3:08pm UTC](https://discuss.elastic.co/t/es-2-3-3-node-cannot-join-the-master-node/55061 "2016-07-08T15:08:58Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![arek](https://avatars.discourse-cdn.com/v4/letter/a/46a35a/32.png) [@arek](https://discuss.elastic.co/u/arek)\
**Post date:** [July 8, 2016, 3:08pm UTC](https://discuss.elastic.co/t/es-2-3-3-node-cannot-join-the-master-node/55061/1 "2016-07-08T15:08:58Z")

</div>

Hi,  
I configured simple two-node cluster (for test purposes) with one master node. It's Red Hat servers. Unfortunately second node cannot join to the master node. Here is configuration of master node:

```
cluster.name: elksandpit
node.name: "sandpit1"
node.master: true
node.data: true
path.data: /var/opt/elk_storage/data
path.work: /var/opt/elk_storage/work
path.logs: /var/opt/elk_storage/logs
bootstrap.mlockall: true
discovery.zen.ping.multicast.enabled: false
discovery.zen.ping.unicast.hosts: ["127.0.0.1"]
transport.tcp.port: 9300
network.publish_host: aa.bbc.ccc.228 //I am hiding IP in post for privacy

```

And here is configuration of second node, this node is design only for Kibana:

```
cluster.name: elksandpit
node.name: "kibana"
node.master: false
node.data: false
bootstrap.mlockall: true
discovery.zen.ping.multicast.enabled: false
discovery.zen.ping.unicast.hosts: ["aa.bbb.ccc.228:9300"]
transport.tcp.connect_timeout: 2m
network.publish_host: aa.bbb.ccc.226

```

When I'm executing this from second node (not master):

`curl -XGET localhost:9200/_cat/health`  
error appears:  
`{"error":{"root_cause":[{"type":"master_not_discovered_exception","reason":null}],"type":"master_not_discovered_exception","reason":null},"status":503}`

```
MasterNotDiscoveredException[null]
        at org.elasticsearch.action.support.master.TransportMasterNodeAction$AsyncSingleAction$5.onTimeout(TransportMasterNodeAction.java:226)
        at org.elasticsearch.cluster.ClusterStateObserver$ObserverClusterStateListener.onTimeout(ClusterStateObserver.java:236)
        at org.elasticsearch.cluster.service.InternalClusterService$NotifyTimeout.run(InternalClusterService.java:804)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
        at java.lang.Thread.run(Thread.java:745)

```

If somebody could give any hint. Thanks.

---

<div class="post-metadata">

**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:** [July 10, 2016, 6:17am UTC](https://discuss.elastic.co/t/es-2-3-3-node-cannot-join-the-master-node/55061/2 "2016-07-10T06:17:50Z")

</div>

> [@arek](#):
>
> discovery.zen.ping.multicast.enabled: false

You do not needs this in 2.X, multicast doesn't exist in core.

> [@arek](#):
>
> transport.tcp.port: 9300

And this is the default, so no need to specify it either.

Are both hosts in the same network? Can you `curl aa.bbc.ccc.228:9200` from the `kibana` host?

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [July 10, 2016, 8:53am UTC](https://discuss.elastic.co/t/es-2-3-3-node-cannot-join-the-master-node/55061/3 "2016-07-10T08:53:36Z")

</div>

network.host is not set here. So it listens only on 127.0.0.1

My 2 cents

---

<div class="post-metadata">

**Author:** ![arek](https://avatars.discourse-cdn.com/v4/letter/a/46a35a/32.png) [@arek](https://discuss.elastic.co/u/arek)\
**Post date:** [July 11, 2016, 10:31am UTC](https://discuss.elastic.co/t/es-2-3-3-node-cannot-join-the-master-node/55061/4 "2016-07-11T10:31:25Z")

</div>

Hi,  
thank you for replaying  
When I'm executing  
`curl aa.bbb.ccc.228:9200`

from kibana host I'm getting  
`curl: (7) couldn't connect to host`

Is setting network.host option (+removing unnecessary configuration entries) on both machines remedy for my issue ?

(Just asking, not checking this, because I lost root privileges for one day or two and waiting till our infrastucture grant me root again....)  
Thanks!

---

<div class="post-metadata">

**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:** [July 11, 2016, 10:49am UTC](https://discuss.elastic.co/t/es-2-3-3-node-cannot-join-the-master-node/55061/5 "2016-07-11T10:49:42Z")

</div>

> [@arek](#):
>
> Is setting network.host option (+removing unnecessary configuration entries) on both machines remedy for my issue ?

It will help!

---

<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:** [July 5, 2017, 10:36pm UTC](https://discuss.elastic.co/t/es-2-3-3-node-cannot-join-the-master-node/55061/6 "2017-07-05T22:36:37Z")

</div>