Bug #102258 | Incorrect error while trying to download binary log from a certain position | ||
---|---|---|---|
Submitted: | 15 Jan 2021 14:42 | Modified: | 18 Jan 2021 12:04 |
Reporter: | Niranjan R | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server | Severity: | S3 (Non-critical) |
Version: | 5.7 | OS: | Any |
Assigned to: | MySQL Verification Team | CPU Architecture: | Any |
[15 Jan 2021 14:42]
Niranjan R
[15 Jan 2021 19:40]
Simon Mudd
If you use the wrong binlog position all bets are off. The binlog stream is a binary streaam with a reasonably well defined format but there are no explicit message delimiters. The first part of the message includes its length, so if you jump into a random position this may make mysqlbinlog simply interpret the data as having a very large packet. That's wrong as the "input data" is wrong. So special care is required to ensure and verify that the binlog position you specify is correct as otherwise correct processing is impossible given that the binlog file has no easy to recognise delimiters.
[18 Jan 2021 12:04]
MySQL Verification Team
Hi, This is not a bug. If you use wrong position we cannot find the start/end and the read data can be (will be) larger than max packet size so the error is "correct". all best Bogdan