Connection Pool Exhaustion
criticalContainedcapacity failure · fan out propagation
Blast Radius
6%
1/18 nodes
Time to Detect
Seconds if pool saturation alerting is configured. Minutes if only detected through latency monitors or user reports.
Preventive Mitigations
2
Confidence
StrongImpacted Components
Redis
cache · Directly connected to failure mode 'Connection Pool Exhaustion' via risk propagation path in the topology.
Failure Cascade
Redis
Connection Pool Exhaustion (fan out propagation) directly affects these components.
Severity at this step: critical
Detection Signals
Recovery time estimate: Seconds once blocking queries are terminated. Minutes if waiting for natural query completion.
Mitigation Checklist(2 preventive, 5 reactive)
Total connections across all app replicas must not exceed database max_connections minus administrative headroom (typically 10–20%). pool_size_per_replica × replica_count < max_connections × 0.8
PgBouncer multiplexes thousands of client connections to a small server-side pool. App replicas connect to PgBouncer (cheap), which routes to PostgreSQL (expensive).
Open the circuit when pool wait time exceeds threshold, failing fast rather than queuing requests that will time out anyway.
A connection pool bounds the total database connections an application can open, preventing connection storms during traffic spikes and protecting the database server from exceeding its connection limit.
PgBouncer multiplexes many client connections onto a small pool of PostgreSQL server connections, directly preventing connection exhaustion by bounding the number of server connections regardless of client count.
Rate limiting bounds the inbound request rate per identity, preventing any single caller from consuming the entire connection pool and exhausting capacity for other callers.
Configure both the connection pool timeout (how long to wait for a connection) and the query timeout (how long a query can run). This prevents connections from being held indefinitely.
Affected Systems
Workloads
Technologies
Blast radius analysis is derived from structured topology and failure mode knowledge. It models structural propagation patterns, not measured production behavior. Actual incident scope depends on runtime conditions, traffic, and recovery actions in place at the time of failure.