3198
MariaDBERRORCommonInnoDB / TransactionsHIGH confidence
Too many concurrent InnoDB transactions
Production Risk
Critical — new transactions cannot start until resolved.
Why it happens
- 1The number of concurrent InnoDB transactions exceeds the internal limit (2^32 - 1).
- 2Extremely high connection count combined with long-running transactions.
How to reproduce
trigger — this will error
trigger — this will error
-- Occurs automatically under extreme concurrent transaction load.
expected output
ERROR 3198 (HY000): Too many concurrent transactions — InnoDB transaction ID limit reached.
Fix 1
Reduce concurrent connections
Reduce concurrent connections
SET GLOBAL max_connections = 500;
Why this works
Fewer connections reduces the peak transaction count.
Fix 2
Commit or rollback idle transactions promptly
Commit or rollback idle transactions promptly
-- Use application-level timeouts to close idle transactions.
Why this works
Reducing transaction lifetime lowers concurrent transaction count.
Fix 3
Perform PURGE or checkpoint
Perform PURGE or checkpoint
-- Allow InnoDB purge thread to advance the transaction ID space.
Why this works
InnoDB reclaims transaction IDs after purge completes.
What not to do
✕
Sources
Official documentation ↗
MySQL 8.0 — 3198 ER_TOO_MANY_CONCURRENT_TRXS
Content generated with AI assistance and reviewed for accuracy. Found an error? hello@errcodes.dev