Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.2(EOL), 10.3(EOL), 10.4(EOL), 10.5(EOL), 10.6, 10.7(EOL)
-
Not for Release Notes
Description
# mysqld options required for replay: --log_bin
|
SHOW BINLOG EVENTS FROM 120;
|
Leads to:
|
10.7.0 71ed8c136fa203b9b3a678a6d5cc72235ef73ef7 (Debug) |
10.7.0-dbg>SHOW BINLOG EVENTS FROM 120;
|
ERROR 1220 (HY000): Error when executing command SHOW BINLOG EVENTS: Wrong offset or I/O error
|
Which looks like it could be considered normal; there is a wrong offset. However, in the error log we see:
|
10.7.0 71ed8c136fa203b9b3a678a6d5cc72235ef73ef7 (Debug) |
2021-07-29 15:09:04 5 [ERROR] Error in Log_event::read_log_event(): 'Event invalid', data_len: 0, event_type: 0
|
Which is quite cryptic and does not much align with the CLI based error. If not a bug (likely) can we improve the error log message to read similar to the CLI based message?
Also affect tests, as filter for 'Event invalid' is now in place, but this error may happen on real corruption; set prio to major instead of minor.
