You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Browse filesBrowse the repository at this point in the historyBrowse files
Sujatha Sivakumar
committed
Bug#20805298: BINLOG_ERROR_ACTION DOESN'T HANDLE SOME
FAILURES DURING BINLOG ROTATION
Analysis:
========
In case of hardware errors in binlog partition during binlog
rotate, we can see the following error being reported.
[ERROR] The server was unable to create a new log file. An
incident event has been written to the binary log which will
stop the slaves.
[ERROR] Can't generate a unique log-filename
master-bin.(1-999)
All replicas break either due to seeing incident event or
simply because the dump thread cannot access binlog
partition. binlog_error_action was developed for these
purposes (i,e; to avoid server accepting writes even though
binlog writes are failing), but it doesn't handle the above
case.
Fix:
===
An error handler has been added in such a way that, on
hardware failure during rotate, it will do the specific
action defined as part 'binlog_error_action' variable.
Also incident event will not be written to the binary log
in the above mentioned scenario.
0 commit comments