innodb_print_all_deadlocks
INFO
Rule IDs: mi_001
Overview
- Purpose
- Documented in the MySQL 8.4 manual as a server system variable (scope: Global). Purpose and semantics are described at the linked manual page.
- Dynamic (MySQL 8.4 reference)
- MySQL 8.4 marks this variable as dynamic (
Dynamic= Yes). Runtime changes useSET GLOBAL(global scope) orSET SESSION(session scope) — confirm syntax and persistence (SET PERSIST) in the manual. - Default value
- OFF (MySQL 8.4)
- Version and product notes
- MariaDB and Percona Server may use different names, defaults, or dynamic behavior; verify their documentation.
- Documentation
- https://dev.mysql.com/doc/refman/8.4/en/innodb-parameters.html#sysvar_innodb_print_all_deadlocks
- Other vendors
What is checked
Rules that reference this variable, with their severity and what each rule detects:
- INFO
mi_001: Enable innodb_print_all_deadlocks=ON to log all deadlocks to the error log for post-mortem analysis.
Tuning guidance
- Recommended actions:
- Enable innodb_print_all_deadlocks=ON to log all deadlocks to the error log for post-mortem analysis.
- Trade-offs: Validate recommendations against monitoring, workload profiles, and vendor documentation before making changes.
Example
SET GLOBAL innodb_print_all_deadlocks = ON;
-- Logs all deadlocks to error log
Always validate on a non-production instance first. Use SET PERSIST (MySQL 8.0+) for changes that should survive restarts.