I am connecting to single instance of Elastic Search server remotely via
Transport client.
In my web application which makes use of Transport client, i am see
following messages in the logs:
I have checked, my network connection is proper and ES server is up. But
still getting these messages
Maybe you use a network filter / firewall which is misconfigured - no
connection is possible, everything seems to time out.
You must open TCP and UDP on port 9300 on all the hosts of the cluster
nodes if you use TransportClient.
Also check if your network can operate regarding other nodes, if
Thanks for the reply. I am facing this error intermittently. Transport
Client works fine sometimes - so it rules out firewall or port related
issues.
I have only one ES node (version 1.1.1)
- Firewall is not configured
- TCP and UDP on port 9300 are open
- sniff is disabled (I 'm using default
Can you manually test all of that using telnet?
Regards,
Mark Walkom
Infrastructure Engineer
Campaign Monitor
email: ma...@campaignmonitor.com
web: www.campaignmonitor.com
On 16 September 2014 20:09, Abhishek Aggarwal boyobo...@gmail.com wrote:
Thanks for the reply. I am facing this error
We are also facing this kind of issue in es version 1.1.1.
Some node gets disconnected and while analyzing the logs in that
disconnected node we got a lot connection time out error. So sometime
this issue gets solved by restarting the master node, but sometime we may
need to restart the whole
