Static Connection Pool in C# NEST Client

Hi All,

I have a cluster set up which contains 3 nodes which are all master and data nodes.

The current C# code for CRUD index operations and searching uses a ConnectionSettings object which only specifies a single URI for Node 1 in the cluster and as such I assume all request traffic will be hitting this node?

I'm also assuming that if this Node 1 were to go down then the requests would start failing because it is referencing only the URI of Node 1 in the code?

Should I make a change to instead use a StaticConnectionPool containing the URI of each of my 3 nodes? Will this provide load balancing of requests as they should be farmed out in a round-robin fashion? Or does Elasticsearch load balance requests automatically if I continue to send all requests to Node 1?

Thanks in advance.

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