Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 5.3.12, 5.5.34, 10.0.7
-
Fix Version/s: 5.5.35
-
Component/s: None
-
Labels:None
Description
Replication slaves that support binlog checksums try setting master_binlog_checksum on the master, but that fails if the master does not support checkums. This causes a warning to be written to the slave's error log if the the slave is running with log_warnings enabled. See MDEV-3155
There should be an option that disables this behavior on the slave. It is obnoxious to have hundreds of these messages written to the slave's error log and that risks masking legitimate errors that require an administrator's attention.
Perhaps if the slave is running with binlog_checksum=NONE, it should not attempt to set master_binlog_checksum on the master? Or maybe there should be a new option to explicitly disable this behavior on the slave.
Gliffy Diagrams
Attachments
Issue Links
- relates to
-
- Closed
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
Fixed by not writing entries to slave log if log_warnings is <=1
What we could easily do is to mask this "expected" error and only show it in the log if one runs with --log-warnings=2 (MariaDB supports many log-warnings levels).
This should solve the issue, and at the same time still allow people to get this error if they would ever need to do more high level debugging (by running with a higher warning level).
I will implement this for next MariaDB 5.5 release.