How to Discuss Database Connection Pool Exhaustion in English

Connection pool exhaustion produces symptoms — timeouts, “too many connections” errors, requests hanging — that look like a dozen other problems, so being able to name it precisely and explain why it happened is what actually shortens an incident instead of prolonging the guessing.

Key Vocabulary

Connection pool — a fixed set of pre-established database connections an application reuses across requests instead of opening a new connection for every single query, which would be far too slow and resource-intensive at scale. “The connection pool is set to 20 connections — under normal load that’s plenty, but during this traffic spike, every one of those connections was checked out and requests started queuing.”

Pool exhaustion — the state where every connection in a pool is in use and a new request has none available to borrow, forcing it to wait (or time out) instead of executing immediately. “This isn’t a database performance problem — it’s pool exhaustion. The database itself is responding fine, but our application ran out of connections to send it more queries with.”

Connection leak — a bug where a connection is checked out from the pool but never returned, gradually shrinking the pool’s effective size until exhaustion happens even under normal traffic. “We’re not actually under heavy load right now — this is a slow connection leak. Some code path is checking out a connection on error and never releasing it back to the pool.”

Queueing (at the pool) — the behavior of new requests waiting for a connection to become available rather than failing immediately, which delays failures and can make a pool exhaustion incident look like general slowness before it becomes outright timeouts. “Response times crept up for ten minutes before the timeouts started — that’s requests queueing at the pool waiting for a connection, and once the queue itself hit its limit, they started failing outright.”

Common Phrases

• “Is this pool exhaustion, or is the database itself actually slow?”
• “Are we leaking connections somewhere, or is this just legitimate load?”
• “How big is the connection pool, and is that even enough for our traffic?”
• “Are requests queueing at the pool, or failing immediately?”
• “Which code path is checking out a connection without releasing it?”

Example Sentences

Diagnosing the issue during an incident call: “Database CPU and query latency both look completely normal — this is pool exhaustion on the application side, not a database problem. We’ve got a fixed pool of 20 connections and roughly 60 concurrent requests trying to use them.”

Explaining a root cause after investigation: “We found the actual cause — it’s a connection leak in the reporting job. When that job hits an error, it returns early without releasing its connection back to the pool. Over a few hours, that slowly starves the pool down to nothing.”

Describing the fix in a postmortem: “We fixed the immediate issue by adding a finally block to guarantee the connection is always released, leak or no leak. We also increased the pool size as a buffer and added an alert for pool utilization crossing 80%, so we catch the next leak before it becomes an outage.”

Professional Tips

• Say pool exhaustion, not “the database is slow,” when connection metrics confirm it — it correctly points investigation at the application’s connection handling instead of the database itself.
• Distinguish a connection leak from ordinary high traffic explicitly — a leak degrades gradually and independently of load, while exhaustion from real traffic scales with request volume, and the fixes are completely different.
• Mention whether requests are queueing or failing outright when describing symptoms — queueing produces gradually rising latency before hard failures, which is a distinct and diagnostically useful pattern.
• In a postmortem, name the exact code path responsible for a leak, not just “we found a leak” — it makes the fix verifiable and the pattern searchable for similar bugs elsewhere in the codebase.

Practice Exercise

1. Write a sentence explaining the difference between pool exhaustion from real traffic and pool exhaustion from a connection leak.
2. Explain what queueing at the pool looks like from a user’s perspective before it becomes outright failures.
3. Describe how you’d phrase a postmortem action item for preventing a similar leak in the future.