# TCP connection limit of Elasticsearch

**URL:** <https://discuss.elastic.co/t/tcp-connection-limit-of-elasticsearch/271454>\
**Category:** Elasticsearch\
**Created:** [April 28, 2021, 3:28am UTC](https://discuss.elastic.co/t/tcp-connection-limit-of-elasticsearch/271454 "2021-04-28T03:28:26Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![iammanmale](https://avatars.discourse-cdn.com/v4/letter/i/5e9695/32.png) [@iammanmale](https://discuss.elastic.co/u/iammanmale)\
**Post date:** [April 28, 2021, 3:28am UTC](https://discuss.elastic.co/t/tcp-connection-limit-of-elasticsearch/271454/1 "2021-04-28T03:28:26Z")

</div>

We harvest logs on aws machines by filebeat. Filebeat on each machine push those log to local logstash nodes and then logstash nodes push the data to local Elasticsearch nodes. It seems to me that both logstash node and Elasticsearch nodes have no of tcp connection limit. Each logstash node cannot accept more than around 100 tcp connections with filebeat in aws machines. Something like that also happen on Elasticsearch nodes, each ES node cannot form more than around 100 tcp connections with logstash node. Timeout error will occurs in tcp connection exceed around 100 or more. Is there any way to increase no of tcp connection? is it a parameter of jvm or linux itself?

---

<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 26, 2021, 3:29am UTC](https://discuss.elastic.co/t/tcp-connection-limit-of-elasticsearch/271454/2 "2021-05-26T03:29:18Z")

</div>

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