Hi, I'm seeing connection failures using Sniffing ConnectionPool , where parts of the elasticsearch cluster is only available on the http port, that is - the transport port is closed for these nodes. When limiting the set of cluster nodes to only those with open transport ports, no failed sniffing …

Elasticsearch.Net SniffingConnectionPool requires open Transport port

system (system) Closed April 8, 2017, 10:21pm 6

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

Topic		Replies	Views
Elasticsearch.net 5.0 Beta1, SniffingConnectionPool - Failed sniffing cluster state Elasticsearch	2	900	July 5, 2017
Transport client sniff - AWS Elasticsearch	5	1735	July 6, 2017
Java API : Transport client not complaining when no cluster is on Elasticsearch	3	335	July 6, 2017
Unable to perform search in Elasticsearch, error "Failed sniffing cluster state." Elasticsearch	1	1438	October 31, 2018
Problems connecting with other nodes Elasticsearch	2	1134	July 6, 2017