log_replica_updates
WARNING
Rule IDs: bl_008
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 not dynamic (
Dynamic= No). It must be set inmy.cnfor on the command line; changing it requires a restart. - Default value
- ON (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/replication-options-binary-log.html#sysvar_log_replica_updates
- Other vendors
What is checked
Rules that reference this variable, with their severity and what each rule detects:
- WARNING
bl_008: Enable log_replica_updates=ON when using GTID-based replication.
Tuning guidance
- Recommended actions:
- Enable log_replica_updates=ON when using GTID-based replication.
- Trade-offs: Binary logging is essential for replication and point-in-time recovery. sync_binlog=1 guarantees durability but adds fsync overhead. ROW format is safest for replication consistency but produces larger binlogs.
Example
Configure in my.cnf (or equivalent) or server startup options, then restart.