1.2 KiB
1.2 KiB
title, keywords, summary, category, source, breadcrumb, kb_scope, covers, when_to_retrieve
| title | keywords | summary | category | source | breadcrumb | kb_scope | covers | when_to_retrieve | |||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| MySQL Connection Pool Runbook |
|
Diagnose exhausted MySQL connection pools and distinguish application leaks from database limits. | database | mysql-connection-pool | Database > MySQL > Connection Pool | rag-eval |
|
Use when MySQL clients report exhausted pools, connection acquisition timeout, max_connections pressure, or HikariCP saturation. |
Database
MySQL
Connection Pool
When MySQL connection pool is exhausted, first compare application pool usage with database max_connections.
For HikariCP, check active, idle, pending, and connection acquisition timeout metrics.
Recommended diagnosis:
- Verify whether HikariCP active connections stay near maximum while pending threads grow.
- Check MySQL
Threads_connected,Threads_running, andmax_connections. - Inspect slow SQL and long transactions that keep connections checked out.
- If the database is healthy, look for application connection leaks or missing transaction boundaries.
Use this runbook as evidence for connection pool, max_connections, and HikariCP incidents.