# Elasticsearch OpenJDK process takes over every available TCP port

**URL:** <https://discuss.elastic.co/t/elasticsearch-openjdk-process-takes-over-every-available-tcp-port/261107>\
**Category:** Elasticsearch\
**Created:** [January 14, 2021, 10:30am UTC](https://discuss.elastic.co/t/elasticsearch-openjdk-process-takes-over-every-available-tcp-port/261107 "2021-01-14T10:30:29Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [January 17, 2021, 12:22pm UTC](https://discuss.elastic.co/t/elasticsearch-openjdk-process-takes-over-every-available-tcp-port/261107/4 "2021-01-17T12:22:20Z")

</div>

Every Elasticsearch node will open 10-13 TCP channels to every other node in the cluster, and ≤18 TCP channels to any remote clusters. This is normal behaviour and even in a very large cluster it wouldn't be enough for you to run out of local ports.

---

_[View the full topic](https://discuss.elastic.co/t/elasticsearch-openjdk-process-takes-over-every-available-tcp-port/261107)._