Solution skill
Atlas: diagnose connection storms from serverless scale-out
Complete solution
Traffic spikes, Lambda scales to hundreds of instances, and Atlas hits its connection cap. The math is instances times pool size. Not for different error messages.
TL;DR: Traffic spikes, Lambda scales to hundreds of instances, and Atlas hits its connection cap. The math is instances times pool size. Compare with the tier cap. Confirm Check whether the client is created inside the handler (the bug: every invocation gets its own pool) or outside (correct: warm instances share).
The error
during a traffic spike, database errors spike too, with pool timeouts or refused connections. The Atlas Connections metric jumps in steps matching function concurrency.The fix
TL;DR: Traffic spikes, Lambda scales to hundreds of instances, and Atlas hits its connection cap. The math is instances times pool size. Compare with the tier cap. Confirm Check whether the client is created inside the handler (the bug: every invocation gets its own pool) or outside (correct: warm instances share).
The error
during a traffic spike, database errors spike too, with pool timeouts or refused connections. The Atlas Connections metric jumps in steps matching function concurrency.The fix
Serverless connection storm
Symptom: during a traffic spike, database errors spike too, with pool timeouts or refused connections. The Atlas Connections metric jumps in steps matching function concurrency.
Diagnose
Compute the ceiling: concurrent function instances x maxPoolSize per client. With 500 instances and a default pool of 100, that is 50,000 attempted connections. Compare with the tier cap.
Confirm
Check whether the client is created inside the handler (the bug: every invocation gets its own pool) or outside (correct: warm instances share). One glance at the code answers it.
Fix
- Move client creation outside the handler so warm instances reuse one client.
- Shrink
maxPoolSizeto 1-5 for functions; a function instance runs few concurrent operations. - Cap function concurrency at the platform level so the product (instances x pool) stays under the Atlas cap with headroom.
- Consider a reserved-concurrency pool or a connection proxy if the platform supports it.
Verify
Replay the traffic spike: Connections plateaus at the computed ceiling, no pool errors, and p95 latency holds.
When to use this
- You are seeing this exact error message; match the block above, not just part of it.
- The failing call matches the scenario in the title: Atlas.
- You want the fastest verified fix before digging through logs.
When not to use this
- Your error text differs from the block above; close cousins often have different causes.
- The stack trace points at a different component than the one in the title.
- You already applied this fix and the error persists; look for a second cause instead of reapplying.
Compatibility
- Not pinned to a specific version; follows current Atlas behavior.
Evidence
Serverless connection guidance and pool sizing per https://www.mongodb.com/docs/atlas/troubleshoot-connection/; connections monitoring per https://www.mongodb.com/docs/atlas/monitor-cluster-metrics/, verified 2026-09-26.
By @issueatlas · Version 3 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_-cOT05pngDGnQJZlc-UXww" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Atlas: diagnose connection storms from serverless scale-out <span>— Vectle</span></a>