MasterNotDiscoveredException after extending disk space

Elastic Stack Elasticsearch
1

Hi all,

We have Elasticsearch deployed in 2 nodes, and we had issue related to disk space, and after extending it, we get the following issue MasterNotDiscoveredException[waited for [30s]].

[2018-07-06 10:02:35,466][WARN ][discovery.zen.ping.unicast] [***server_name***] failed to send ping to [[***server_name***][*********][***server_name***][inet[/10.14.**.**:9300]]]
org.elasticsearch.transport.SendRequestTransportException: [***server_name***][inet[/10.14.**.**:9300]][internal:discovery/zen/unicast]
	at org.elasticsearch.transport.TransportService.sendRequest(TransportService.java:286)
	at org.elasticsearch.shield.transport.ShieldServerTransportService.sendRequest(ShieldServerTransportService.java:59)
	at org.elasticsearch.discovery.zen.ping.unicast.UnicastZenPing.sendPingRequestToNode(UnicastZenPing.java:468)
	at org.elasticsearch.discovery.zen.ping.unicast.UnicastZenPing.access$1000(UnicastZenPing.java:62)
	at org.elasticsearch.discovery.zen.ping.unicast.UnicastZenPing$3.run(UnicastZenPing.java:383)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:745)
Caused by: org.elasticsearch.transport.NodeNotConnectedException: [***server_name***][inet[/10.14.**.**:9300]] Node not connected
	at org.elasticsearch.transport.netty.NettyTransport.nodeChannel(NettyTransport.java:964)
	at org.elasticsearch.transport.netty.NettyTransport.sendRequest(NettyTransport.java:656)
	at org.elasticsearch.transport.TransportService.sendRequest(TransportService.java:276)
	... 7 more

Note: for security reasons, we hide some informations by using "*".

Please give me some help

Thank you in advance.

Best regards,
Mohammed ESSABRI

2

This is the crucial line:

The node is not connected. There should be other information in the log indicating why this might be. I'd start by looking for connections being refused, or connection timeouts, and also confirm that the IP addresses are all correct and that discovery.zen.ping.unicast.hosts is set correctly on both nodes.

3

Thank you for the help @DavidTurner,

Right, it was related to neetwork issue.

Many thanks!

1 Like
4

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