MongoDB Atlas: size the connection pool deliberately
Shows how to fix mongoDB Atlas: size the connection pool deliberately. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
Check slow queries first; raising maxPoolSize on top of slow queries just moves the bottleneck. - minPoolSize above 0 avoids connect latency on burst traffic, at the cost of idle connections.
Steps
- Every driver keeps a pool per client. The knobs, in every driver:
- -
maxPoolSize(default 100): ceiling on connections per client.
minPoolSize(default 0): warm connections kept ready.maxIdleTimeMS: how long an idle connection lives before being recycled.waitQueueTimeoutMS: how long an operation waits for a free connection before erroring.
- Total connections = clients x maxPoolSize. Count your clients: app instances, workers, serverless concurrency, plus mongosh sessions and tools. Size maxPoolSize from expected concurrent database operations per client, not from the default.
- - One client per process keeps the math simple. N clients with default pools is how you accidentally open 500 connections.
- If you see wait-queue timeouts under load, the pool is too small OR operations are too slow. Check slow queries first; raising maxPoolSize on top of slow queries just moves the bottleneck.
minPoolSizeabove 0 avoids connect latency on burst traffic, at the cost of idle connections. Use it for latency-sensitive services.- Lower
maxIdleTimeMS(a few minutes) when clients sit behind load balancers or NATs that silently drop idle TCP connections.
- Watch Atlas Metrics, Connections, under real load. Steady near your computed ceiling is healthy; sawtooth or plateau-at-cap with errors means resize.
When to use
You are seeing this: Every driver keeps a pool per client. Use this skill when you run into "MongoDB Atlas: size the connection pool deliberately".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.
Why this happens
The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
Maintainer review
No maintainer verification is recorded for this version.
This records the version a maintainer checked. It does not assert that the version is the latest upstream release.