Transport Client + Connection Pool + TCP/IP Connection Leakages


We are using transport client for connecting to Elastic Search from our microservices; Off late we ran into issue of number of Open TCP/IP connections are growing with addition of Microservices. This is causing issues related to manage our VMs. After certain amount of Open TCP/IP Connections, VMs are not reachable and hence application is not stable.

We have close to around 8 microservices, each having a Singleton instance of TransportClient; With the time, number of open TCP/IP connection increases gradually. All these connections are related to ES as per VM logs. We create a singleton instance of Transport client on server startup and close the transport client on stopping the server.

We have not touched any other configuration related to number of connection in Transport client. Appreciate any valuable feedback to identify the bottleneck.


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