Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.4(EOL), 10.5, 10.6, 10.9(EOL), 10.10(EOL), 10.11, 11.0(EOL), 11.1(EOL), 11.2(EOL), 11.3(EOL), 11.4
Description
# mysqld options required for replay: --log-bin |
SHOW BINLOG EVENTS FROM 500; |
Leads to, on the client:
|
11.3.0 126157061b4376496c034a809ea4943e863d1465 (Optimized) |
11.3.0-opt>SHOW BINLOG EVENTS FROM 500;
|
ERROR 1220 (HY000): Error when executing command SHOW BINLOG EVENTS: Wrong offset or I/O error
|
Which is easy to understand and correct. However the error log shows, on optimized builds:
|
11.3.0 126157061b4376496c034a809ea4943e863d1465 (Optimized) |
2023-10-31 16:00:27 5 [ERROR] Error in Log_event::read_log_event(): 'Event too big', data_len: 117440512, event_type: 0
|
Here there is no correlation between what actually happened (a harmless SQL statement failure) and the error shown in the error log (which looks like an important binlog failure & possible corruption).
The debug log shows:
|
11.3.0 126157061b4376496c034a809ea4943e863d1465 (Debug) |
2023-10-31 15:58:56 5 [ERROR] Replication event checksum verification failed while reading from a log file
|
2023-10-31 15:58:56 5 [ERROR] Error in Log_event::read_log_event(): 'Replication event checksum verification failed while reading from a log file', data_len: 41, event_type: 0
|
10.4 Optimized shows the same output as debug in later versions:
|
10.4.32 e52777f1a4df20ffd3ae743b7b64f5e645090cd8 (Optimized) |
2023-10-31 16:06:21 10 [ERROR] Replication event checksum verification failed while reading from a log file
|
2023-10-31 16:06:21 10 [ERROR] Error in Log_event::read_log_event(): 'Replication event checksum verification failed while reading from a log file', data_len: 41, event_type: 0
|
Which again looks severe but is harmless. It would be good if we can improve the output to show it was a harmless issue.
Attachments
Issue Links
- relates to
-
MDEV-21839 Handle crazy offset to SHOW BINLOG EVENTS
-
- Closed
-