max_allowed_packet
WARNING (2 rules)
Rule IDs: mem_008, net_001
Overview
- Purpose
- Documented in the MySQL 8.4 manual as a server system variable (scope: Both). 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
- 67108864 (64 MB) (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/server-system-variables.html#sysvar_max_allowed_packet
- Other vendors
What is checked
Rules that reference this variable, with their severity and what each rule detects:
- WARNING
mem_008: Set max_allowed_packet to at least 16MB. 64MB (MySQL 8.0 default) is safe for most workloads. - WARNING
net_001: Set max_allowed_packet to at least 16MB. 64MB (MySQL 8.0 default) is safe for most workloads.
Tuning guidance
- Recommended actions:
- Set max_allowed_packet to at least 16MB. 64MB (MySQL 8.0 default) is safe for most workloads.
- Trade-offs: Per-thread buffers are allocated per-session on demand. Large values waste memory when multiplied by max_connections. Small values cause disk spills for complex queries. Tune based on query profiles, not guesswork.
Example
SET GLOBAL max_allowed_packet = 67108864; -- 64 MB
Always validate on a non-production instance first. Use SET PERSIST (MySQL 8.0+) for changes that should survive restarts.