using NEST or ElasticsearchClient (1.9,2) outputting trace diagnostics from .net services I'm running to into port exhaustion problems.
netstat -ano | findstr 9200 | measure-object -line
yields well over 5000 established ports to the server. This number can reach over 10,000
I'm using both IndexAsync and BulkAsync - I dont care what the response is, only that the request was successfully submitted.
Hey @amccool What version of Elasticsearch are you running against?
You can use ConnectionLimit in NEST 2.x and 5.x to control the number of open TCP connections to an endpoint, but this is hardcoded in NEST 1.x to be 10,000:
You can however provide your own implementation of IConnection that derives from HttpConnection and override the AlterServicePoint method to set ConnectionLimit to a more reasonable number e.g. 80 as per 2.x and 5.x.
Then pass it to the constructor for ElasticClient to use it
var uri = new Uri("http://localhost:9200");
var settings = new ConnectionSettings(uri, defaultIndex: "default-index");
var client = new ElasticClient(settings, new CustomHttpConnectionWithLowerConnectionLimit(settings));
TCP connection pooling is managed by the .NET framework, so connections should be being reused already. In full .NET framework, this is controlled by ServicePointManager, and the framework will queue up a request on a connection until one becomes available.