[MDEV-26270] Unclear error log message when using invalid SHOW BINLOG EVENTS offset Created: 2021-07-29  Updated: 2023-04-27

Status: Open
Project: MariaDB Server
Component/s: Replication
Affects Version/s: 10.2, 10.3, 10.4, 10.5, 10.6, 10.7
Fix Version/s: 10.4, 10.5, 10.6

Type: Bug Priority: Major
Reporter: Roel Van de Paar Assignee: Andrei Elkin
Resolution: Unresolved Votes: 0
Labels: affects-tests, improvement


 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.

 Comments   
Comment by Andrei Elkin [ 2022-01-29 ]

sujatha.sivakumar, as SBE is your loyal client :--), could you please take on this discrepancy between the user and server error?

Generated at Thu Feb 08 09:44:01 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.