[MDEV-18155] Bogus 'Event truncated', 'Event too big', 'Event invalid' upon SHOW BINLOG EVENTS FROM <pos> Created: 2019-01-06  Updated: 2021-09-30  Resolved: 2020-09-22

Status: Closed
Project: MariaDB Server
Component/s: Replication
Affects Version/s: 10.3, 10.4, 10.5
Fix Version/s: 10.1.48, 10.2.35, 10.3.26, 10.4.16, 10.5.7

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Sujatha Sivakumar (Inactive)
Resolution: Fixed Votes: 1
Labels: None

Attachments: File event_invalid.test     File event_too_big.test     File event_truncated.test    

 Description   

All attached test cases end with SHOW BINLOG EVENTS FROM 10000, which in all cases causes ER_ERROR_WHEN_EXECUTING_COMMAND with the text Wrong offset or I/O error. Maybe the offset is really wrong, but I don't suppose it should produce the errors in the error log hinting at corruption:

10.3 faf206a848

 
2019-01-06 20:48:36 5 [ERROR] Error in Log_event::read_log_event(): 'Event truncated'

10.3 faf206a848

 
2019-01-06 20:49:29 5 [ERROR] Error in Log_event::read_log_event(): 'Event too big', data_len: 1667591269, event_type: 101

10.3 faf206a848

 
2019-01-06 20:49:55 5 [ERROR] Error in Log_event::read_log_event(): 'Event invalid', data_len: 0, event_type: 52

Certainly there are no big events in the binary logs, and I don't think any of them are invalid.

I've set the affects versions to 10.3+, because the test case is essentially 10.3-specific. It's very likely that the failures happen in earlier versions as well. I don't think, however, that it's critical to fix them in prior GA releases.

 Comments   
Comment by Andrei Elkin [ 2020-09-21 ]

sujatha.sivakumar: Hopefully this one is a dup of MDEV-21839. The referred faf206a848 is not a descendant of 873cc1e77a7 just pushed to 10.1
Could you please give it some care?

Comment by Sujatha Sivakumar (Inactive) [ 2020-09-22 ]

Current issue is fixed as part of MDEV-21839.

Verified the attached tests on latest 10.1.47. Observed that appropriate error is reported as shown below.

SHOW BINLOG EVENTS FROM 10000;
ERROR HY000: Error when executing command SHOW BINLOG EVENTS: Invalid pos specified. Requested from pos:10000 is greater than actual file size:9939

Hence closing this issue.

SHOW BINLOG EVENTS FROM 10000;
ERROR HY000: Error when executing command SHOW BINLOG EVENTS: Invalid pos specified. Requested from pos:10000 is greater than actual file size:9571

Comment by Andrei Elkin [ 2020-09-22 ]

sujatha.sivakumar: feels so :sunny:, thank you for that!

Generated at Thu Feb 08 08:41:55 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.