-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Closed
Description
I have not been able to successfully use a SniffingConnectionPool to actually do any sniffing without receiving a timeout error. I can see the calls to /_nodes/_all/clear?timeout=50 and the response looks valid but client returns an error.
var pool = new Elasticsearch.Net.ConnectionPool.SniffingConnectionPool(esNodes.Select(c => new Uri(c)));
var settings = new ConnectionSettings(pool)
.SniffOnStartup(true)
.SniffLifeSpan(TimeSpan.FromMinutes(1))
.SetTimeout(1000)
.MaximumRetries(5);
var client = new ElasticClient(settings: settings);
[WebException: The operation has timed out]
System.Net.HttpWebRequest.GetResponse() +6540964
Elasticsearch.Net.Connection.HttpConnection.DoSynchronousRequest(HttpWebRequest request, Byte[] data, IRequestConfiguration requestSpecificConfig) in c:\Users\gmarz\code\elasticsearch-net\src\Elasticsearch.Net\Connection\HttpConnection.cs:229
[Exception: ping returned no status code]
Elasticsearch.Net.Connection.Transport.Ping(ITransportRequestState requestState) in c:\Users\gmarz\code\elasticsearch-net\src\Elasticsearch.Net\Connection\Transport.cs:85
[PingException: Pinging http://u:p@elasticsearchbox1/ caused an exception]
Elasticsearch.Net.Connection.Transport.Ping(ITransportRequestState requestState) in c:\Users\gmarz\code\elasticsearch-net\src\Elasticsearch.Net\Connection\Transport.cs:96
Elasticsearch.Net.Connection.Transport.DoRequest(TransportRequestState`1 requestState) in c:\Users\gmarz\code\elasticsearch-net\src\Elasticsearch.Net\Connection\Transport.cs:334
Metadata
Metadata
Assignees
Labels
No labels