# Master not discovered exception in my cluster
**URL:** https://discuss.elastic.co/t/master-not-discovered-exception-in-my-cluster/99350
**Category:** Elasticsearch
**Created:** [September 5, 2017, 2:09am UTC](https://discuss.elastic.co/t/master-not-discovered-exception-in-my-cluster/99350 "2017-09-05T02:09:57Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@bigfool1988](https://discuss.elastic.co/u/bigfool1988)
#### Post date: [September 5, 2017, 2:09am UTC](https://discuss.elastic.co/t/master-not-discovered-exception-in-my-cluster/99350/1 "2017-09-05T02:09:57Z")
>
---
### Author:  [@bigfool1988](https://discuss.elastic.co/u/bigfool1988)
#### Post date: [September 5, 2017, 2:12am UTC](https://discuss.elastic.co/t/master-not-discovered-exception-in-my-cluster/99350/2 "2017-09-05T02:12:15Z")
The logs of es55:
[2017-09-04T17:14:00,693][INFO][o.e.n.Node] [es55] initialized
[2017-09-04T17:14:00,693][INFO][o.e.n.Node] [es55] starting ...
[2017-09-04T17:14:01,085][INFO][o.e.t.TransportService] [es55] #publish\_address {192.168.3.55:9300}, bound\_addresses {192.168.3.55:9300}
[2017-09-04T17:14:01,141][INFO][o.e.b.BootstrapChecks] [es55] bound or publishing to a non-loopback or non-link-local address, enforcing bootstrap checks
[2017-09-04T17:14:07,704][INFO][o.e.d.z.ZenDiscovery] [es55] failed to send join request to master [{es54}{EfAxONJ2RaOWELG\_yGZNxg}{fW43Cr6bSay8m5B7CRJl2g}{192.168.3.54}{192.168.3.54:9300}], reason [RemoteTransportException[[es54][192.168.3.54:9300][internal:discovery/zen/join]]; nested: NotMasterException[Node [{es54}{EfAxONJ2RaOWELG\_yGZNxg}{fW43Cr6bSay8m5B7CRJl2g}{192.168.3.54}{192.168.3.54:9300}] not master for join request]; ], tried [3] times
[2017-09-04T17:14:13,936][INFO][o.e.d.z.ZenDiscovery] [es55] failed to send join request to master [{es54}{EfAxONJ2RaOWELG\_yGZNxg}{fW43Cr6bSay8m5B7CRJl2g}{192.168.3.54}{192.168.3.54:9300}], reason [RemoteTransportException[[es54][192.168.3.54:9300][internal:discovery/zen/join]]; nested: NotMasterException[Node [{es54}{EfAxONJ2RaOWELG\_yGZNxg}{fW43Cr6bSay8m5B7CRJl2g}{192.168.3.54}{192.168.3.54:9300}] not master for join request]; ], tried [3] times
[2017-09-04T17:14:20,164][INFO][o.e.d.z.ZenDiscovery] [es55] failed to send join request to master [{es54}{EfAxONJ2RaOWELG\_yGZNxg}{fW43Cr6bSay8m5B7CRJl2g}{192.168.3.54}{192.168.3.54:9300}], reason [RemoteTransportException[[es54][192.168.3.54:9300][internal:discovery/zen/join]]; nested: NotMasterException[Node [{es54}{EfAxONJ2RaOWELG\_yGZNxg}{fW43Cr6bSay8m5B7CRJl2g}{192.168.3.54}{192.168.3.54:9300}] not master for join request]; ], tried [3] times
[2017-09-04T17:14:26,389][INFO][o.e.d.z.ZenDiscovery] [es55] failed to send join request to master [{es54}{EfAxONJ2RaOWELG\_yGZNxg}{fW43Cr6bSay8m5B7CRJl2g}{192.168.3.54}{192.168.3.54:9300}], reason [RemoteTransportException[[es54][192.168.3.54:9300][internal:discovery/zen/join]]; nested: NotMasterException[Node [{es54}{EfAxONJ2RaOWELG\_yGZNxg}{fW43Cr6bSay8m5B7CRJl2g}{192.168.3.54}{192.168.3.54:9300}] not master for join request]; ], tried [3] times
[2017-09-04T17:14:31,221][WARN][o.e.n.Node] [es55] timed out while waiting for initial discovery state - timeout: 30s
[2017-09-04T17:14:31,249][INFO][o.e.h.n.Netty4HttpServerTransport] [es55] publish\_address {192.168.3.55:9200}, bound\_addresses {192.168.3.55:9200}
[2017-09-04T17:14:31,250][INFO][o.e.n.Node] [es55] started
[2017-09-04T17:14:32,615][INFO][o.e.d.z.ZenDiscovery] [es55] failed to send join request to master [{es54}{EfAxONJ2RaOWELG\_yGZNxg}{fW43Cr6bSay8m5B7CRJl2g}{192.168.3.54}{192.168.3.54:9300}], reason [RemoteTransportException[[es54][192.168.3.54:9300][internal:discovery/zen/join]]; nested: NotMasterException[Node [{es54}{EfAxONJ2RaOWELG\_yGZNxg}{fW43Cr6bSay8m5B7CRJl2g}{192.168.3.54}{192.168.3.54:9300}] not master for join request]; ], tried [3] times
[2017-09-04T17:14:38,596][DEBUG][o.e.a.a.c.h.TransportClusterHealthAction] [es55] no known master node, scheduling a retry
[2017-09-04T17:14:38,841][INFO][o.e.d.z.ZenDiscovery] [es55] failed to send join request to master [{es54}{EfAxONJ2RaOWELG\_yGZNxg}{fW43Cr6bSay8m5B7CRJl2g}{192.168.3.54}{192.168.3.54:9300}], reason [RemoteTransportException[[es54][192.168.3.54:9300][internal:discovery/zen/join]]; nested: NotMasterException[Node [{es54}{EfAxONJ2RaOWELG\_yGZNxg}{fW43Cr6bSay8m5B7CRJl2g}{192.168.3.54}{192.168.3.54:9300}] not master for join request]; ], tried [3] times
[2017-09-04T17:14:45,066][INFO][o.e.d.z.ZenDiscovery] [es55] failed to send join request to master [{es54}{EfAxONJ2RaOWELG\_yGZNxg}{fW43Cr6bSay8m5B7CRJl2g}{192.168.3.54}{192.168.3.54:9300}], reason [RemoteTransportException[[es54][192.168.3.54:9300][internal:discovery/zen/join]]; nested: NotMasterException[Node [{es54}{EfAxONJ2RaOWELG\_yGZNxg}{fW43Cr6bSay8m5B7CRJl2g}{192.168.3.54}{192.168.3.54:9300}] not master for join request]; ], tried [3] times
[2017-09-04T17:14:51,289][INFO][o.e.d.z.ZenDiscovery] [es55] failed to send join request to master [{es54}{EfAxONJ2RaOWELG\_yGZNxg}{fW43Cr6bSay8m5B7CRJl2g}{192.168.3.54}{192.168.3.54:9300}], reason [RemoteTransportException[[es54][192.168.3.54:9300][internal:discovery/zen/join]]; nested: NotMasterException[Node [{es54}{EfAxONJ2RaOWELG\_yGZNxg}{fW43Cr6bSay8m5B7CRJl2g}{192.168.3.54}{192.168.3.54:9300}] not master for join request]; ], tried [3] times
[2017-09-04T17:14:57,515][INFO][o.e.d.z.ZenDiscovery] [es55] failed to send join request to master [{es54}{EfAxONJ2RaOWELG\_yGZNxg}{fW43Cr6bSay8m5B7CRJl2g}{192.168.3.54}{192.168.3.54:9300}], reason [RemoteTransportException[[es54][192.168.3.54:9300][internal:discovery/zen/join]]; nested: NotMasterException[Node [{es54}{EfAxONJ2RaOWELG\_yGZNxg}{fW43Cr6bSay8m5B7CRJl2g}{192.168.3.54}{192.168.3.54:9300}] not master for join request]; ], tried [3] times
[2017-09-04T17:15:03,738][INFO][o.e.d.z.ZenDiscovery] [es55] failed to send join request to master [{es54}{EfAxONJ2RaOWELG\_yGZNxg}{fW43Cr6bSay8m5B7CRJl2g}{192.168.3.54}{192.168.3.54:9300}], reason [RemoteTransportException[[es54][192.168.3.54:9300][internal:discovery/zen/join]]; nested: NotMasterException[Node [{es54}{EfAxONJ2RaOWELG\_yGZNxg}{fW43Cr6bSay8m5B7CRJl2g}{192.168.3.54}{192.168.3.54:9300}] not master for join request]; ], tried [3] times
[2017-09-04T17:15:08,599][DEBUG][o.e.a.a.c.h.TransportClusterHealthAction] [es55] timed out while retrying [cluster:monitor/health] after failure (timeout [30s])
[2017-09-04T17:15:08,600][WARN][r.suppressed] path: /\_cluster/health, params: {}
org.elasticsearch.discovery.MasterNotDiscoveredException: null
at org.elasticsearch.action.support.master.TransportMasterNodeAction$AsyncSingleAction$4.onTimeout(TransportMasterNodeAction.java:209) [elasticsearch-5.5.1.jar:5.5.1]
at org.elasticsearch.cluster.ClusterStateObserver$ContextPreservingListener.onTimeout(ClusterStateObserver.java:311) [elasticsearch-5.5.1.jar:5.5.1]
at org.elasticsearch.cluster.ClusterStateObserver$ObserverClusterStateListener.onTimeout(ClusterStateObserver.java:238) [elasticsearch-5.5.1.jar:5.5.1]
at org.elasticsearch.cluster.service.ClusterService$NotifyTimeout.run(ClusterService.java:1056) [elasticsearch-5.5.1.jar:5.5.1]
at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:569) [elasticsearch-5.5.1.jar:5.5.1]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0\_131]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0\_131]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0\_131]
---
### Author:  [@poojagupta](https://discuss.elastic.co/u/poojagupta)
#### Post date: [September 5, 2017, 1:14pm UTC](https://discuss.elastic.co/t/master-not-discovered-exception-in-my-cluster/99350/3 "2017-09-05T13:14:58Z")
Hi,
looking at the following lines in lines:
[2017-09-04T17:14:07,704][INFO][o.e.d.z.ZenDiscovery] [es55] failed to send join request to master [{es54}{EfAxONJ2RaOWELG\_yGZNxg}{fW43Cr6bSay8m5B7CRJl2g}{192.168.3.54}{192.168.3.54:9300}], reason [RemoteTransportException[[es54][192.168.3.54:9300][internal:discovery/zen/join]]; nested: NotMasterException[Node [{es54}{EfAxONJ2RaOWELG\_yGZNxg}{fW43Cr6bSay8m5B7CRJl2g
there is problem with es54 node. unable to connect with 192.168.3.54:9300 node. Check 9300 port is in firewall or not?
command for checking it: firewall-cmd --list-ports
if port is not add then add it in the firewall.
for making cluster , 9200 and 9300 both port should be open for communications between nodes.
Also there should be entries of both nodes in /etc/hosts file.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [October 3, 2017, 1:38pm UTC](https://discuss.elastic.co/t/master-not-discovered-exception-in-my-cluster/99350/5 "2017-10-03T13:38:33Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.