# Transport client connections frequently closed in Kubernetes?

**URL:** <https://discuss.elastic.co/t/transport-client-connections-frequently-closed-in-kubernetes/176951>\
**Category:** Elasticsearch\
**Created:** [April 15, 2019, 6:03pm UTC](https://discuss.elastic.co/t/transport-client-connections-frequently-closed-in-kubernetes/176951 "2019-04-15T18:03:36Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Chris\_Gatihi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chris_gatihi/32/25820_2.png) [@Chris\_Gatihi](https://discuss.elastic.co/u/Chris_Gatihi)\
**Post date:** [April 15, 2019, 6:03pm UTC](https://discuss.elastic.co/t/transport-client-connections-frequently-closed-in-kubernetes/176951/1 "2019-04-15T18:03:36Z")

</div>

Hi,

We recently moved to kubernetes our running services that use the Transport client to connect to ES . Our code keeps our transport client connection open unless we have a specific reason to close it (e.g. NoNodeAvailableException) but prior to moving to kubernetes we didn't see these connections being closed (if so, very rarely).

Once we moved to kubernetes, we started seeing these connections being closed frequently and thus we are constantly needing to open new transport client connections.

Has anyone seen such issues with transport client connections being closed in kubernetes? If so, is there a known resolution?

Thanks,  
Chris

---

<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:** [May 13, 2019, 6:03pm UTC](https://discuss.elastic.co/t/transport-client-connections-frequently-closed-in-kubernetes/176951/2 "2019-05-13T18:03:41Z")

</div>

Closed on May 13, 2019, 6:03pm UTC

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