-
-
Notifications
You must be signed in to change notification settings - Fork 526
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pool
settings ignored with mongoDB
#2228
Comments
That is a knex configuration (better say tarn configuration), not used in mongo driver at all. Based on the mongodb typings, it looks like the options are called You can use But based on the docs, the default pool size should be 5, so it sounds weird you would be getting 11 connections. But even if that is not working, it would be an upstream issue. |
As always, thanks for the blazing fast answer! 🚀 |
Let's keep this open, we can definitely map the |
I can confirm that |
Describe the bug
I am trying to limit the number of concurrent connections. I used the
pool
parameter forMikroORM.init
, but it doesn't seem to be used. Instead, 11 connections are opened. I am guessing one is the main em, the 10 others being each RequestContext, but then those connections get reused (?).To Reproduce
MongoDB logs
Expected behavior
I expected a single connection to be created and used.
Versions
The text was updated successfully, but these errors were encountered: