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

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?

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