# Static Connection Pool in C# NEST Client

**URL:** <https://discuss.elastic.co/t/static-connection-pool-in-c-nest-client/89141>\
**Category:** Elasticsearch\
**Created:** [June 13, 2017, 6:00am UTC](https://discuss.elastic.co/t/static-connection-pool-in-c-nest-client/89141 "2017-06-13T06:00:55Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![davey1990](https://avatars.discourse-cdn.com/v4/letter/d/e9c0ed/32.png) [@davey1990](https://discuss.elastic.co/u/davey1990)\
**Post date:** [June 13, 2017, 6:00am UTC](https://discuss.elastic.co/t/static-connection-pool-in-c-nest-client/89141/1 "2017-06-13T06:00:55Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 11, 2017, 6:00am UTC](https://discuss.elastic.co/t/static-connection-pool-in-c-nest-client/89141/2 "2017-07-11T06:00:56Z")

</div>

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