# Node-red-contrib-mongodb4 max concurrent connections, not closing

**URL:** <https://discourse.nodered.org/t/node-red-contrib-mongodb4-max-concurrent-connections-not-closing/72288>\
**Category:** General\
**Created:** [16 December 2022 00:29 UTC](https://discourse.nodered.org/t/node-red-contrib-mongodb4-max-concurrent-connections-not-closing/72288 "2022-12-16T00:29:11Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mrSidX](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/mrsidx/32/18935_2.png) [@mrSidX](https://discourse.nodered.org/u/mrSidX)\
**Post date:** [16 December 2022 00:29 UTC](https://discourse.nodered.org/t/node-red-contrib-mongodb4-max-concurrent-connections-not-closing/72288/1 "2022-12-16T00:29:11Z")

</div>

I'm using `node-red-contrib-mongodb4`, and I an MongoDB Atlas is reporting max connection used (~500).

It seems when I am passing operations to the node it creates a connection, and I can't seem to figure how this is managed.

The background of my setup goes as follows:  
I consolidated all operations to go through 1 mongodb4 node via a sub-flow "MongoDB4" that I'll pass in the `msg.operation=xxx` and collection parameters and payload... I consolidated to one node in this method to attempt to relieve this issue, but here it is.

How can I manage these connections and keep everything minimal?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [14 February 2023 00:29 UTC](https://discourse.nodered.org/t/node-red-contrib-mongodb4-max-concurrent-connections-not-closing/72288/2 "2023-02-14T00:29:40Z")

</div>

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