# Singel Node Opens Too Many Connections

**URL:** <https://discuss.elastic.co/t/singel-node-opens-too-many-connections/233040>\
**Category:** Elasticsearch\
**Created:** [May 18, 2020, 6:32am UTC](https://discuss.elastic.co/t/singel-node-opens-too-many-connections/233040 "2020-05-18T06:32:00Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![chen-wu](https://avatars.discourse-cdn.com/v4/letter/c/ce7236/32.png) [@chen-wu](https://discuss.elastic.co/u/chen-wu)\
**Post date:** [May 18, 2020, 6:32am UTC](https://discuss.elastic.co/t/singel-node-opens-too-many-connections/233040/1 "2020-05-18T06:32:01Z")

</div>

Hello.

We have an instance running in single node running on Windows. I saw that it opens a lot of connections to itself. Like:  
TCP 127.0.0.1:9200 127.0.0.1:52540 ESTABLISHED 21936  
TCP 127.0.0.1:9200 127.0.0.1:52669 ESTABLISHED 21936  
TCP 127.0.0.1:52541 127.0.0.1:52542 ESTABLISHED 21936  
It seems these ports (52540, 52669, 52541, 52542) are random.  
However I have another application uses some port from 50000-60000. This application may stop working if the port is already used.  
Is there any setting to disable this? Or can I modify the setting of this port range?  
I tried http.port, transport.port. But they did not work.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [May 18, 2020, 6:41am UTC](https://discuss.elastic.co/t/singel-node-opens-too-many-connections/233040/2 "2020-05-18T06:41:50Z")

</div>

Welcome! 😃  
What sort of things are connecting to Elasticsearch on that host?

---

<div class="post-metadata">

**Author:** ![chen-wu](https://avatars.discourse-cdn.com/v4/letter/c/ce7236/32.png) [@chen-wu](https://discuss.elastic.co/u/chen-wu)\
**Post date:** [May 18, 2020, 7:07am UTC](https://discuss.elastic.co/t/singel-node-opens-too-many-connections/233040/3 "2020-05-18T07:07:08Z")

</div>

Thanks Warkolm for your reply!  
Nothing is connecting to the instance. I just start it.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [May 18, 2020, 7:08am UTC](https://discuss.elastic.co/t/singel-node-opens-too-many-connections/233040/4 "2020-05-18T07:08:56Z")

</div>

What version are you on?

---

<div class="post-metadata">

**Author:** ![chen-wu](https://avatars.discourse-cdn.com/v4/letter/c/ce7236/32.png) [@chen-wu](https://discuss.elastic.co/u/chen-wu)\
**Post date:** [May 18, 2020, 7:15am UTC](https://discuss.elastic.co/t/singel-node-opens-too-many-connections/233040/5 "2020-05-18T07:15:21Z")

</div>

Sorry for lacking some information.  
Version is 7.5.1. A standalone instance without Kibana or Logstash.  
elasticsearch.yml:

```auto
cluster.name: testing
path.data: C:/ProgramData/es_data/data
path.logs: C:/ProgramData/es_data/logs
network.host: 0.0.0.0
http.port: 9200
transport.port: 9201-9300
discovery.type: single-node

```

---

<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:** [June 15, 2020, 7:15am UTC](https://discuss.elastic.co/t/singel-node-opens-too-many-connections/233040/6 "2020-06-15T07:15:34Z")

</div>

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