Elasticsearch.Net, search gets really slow when one of three nodes are shut down

Hi!

I have a three node cluster on a 7.11.1 Elastic and then I have a .net website doing searches against the index. Everything works just fine but when I shut down one node the search takes about 60 seconds. It feels like Elasticsearch.Net is trying to reach the shut down node, gets a timeout after a minute and the sends the response.
My .net code looks like this:

var nodeUrls = nodeUrl.Split(',');
var nodeUris = nodeUrls.Select(n => new Uri(n));

var nodes = nodeUris.Select(u => new Node(u));
var connectionPool = new StickyConnectionPool(nodes);

var settings = new ConnectionSettings(connectionPool)
    .DisableDirectStreaming()
    .BasicAuthentication(username, password);

var client = new CustomElasticClient(settings);

Can I set the timeout or configure in some way to keep the performance with one node down? Should I use a different type of ConnectionPool?
All threes nodes are configured as master nodes.

Thanks!

/Kristoffer

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