Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
10.4.25, 10.6.9
-
Can result in unexpected behaviour
-
Fixed a problem when replication would break due to the replica sporadically experiencing error "Found invalid event in binary log" while rotating binary logs, despite no invalid event actually being sent to the replica.
-
Q3/2025 Server Development
Description
I got a strange behaviour with replication
Sometimes (I can't reproduce ) the replica stops IO_thread with next error in the log
2022-11-08 13:56:47 87893133 [ERROR] Read invalid event from master: 'Found invalid event in binary log', master could be corrupt but a more likely cause of this is a bug |
2022-11-08 13:56:47 87893133 [ERROR] Slave I/O: Relay log write failure: could not queue event from master, Internal MariaDB error code: 1595 |
2022-11-08 13:56:47 87893133 [Note] Slave I/O thread exiting, read up to log 'mysqld-bin.202006', position 4; GTID position 11-11-48058108793 |
The errors always appear at position 4 , at the start of binlog.
The queries in 11-11-48058108793 and previous statement looks as correct insert/update requests
The replication begins to work after restart replications `stop slave; start slave`
I've attached config file
Attachments
Issue Links
- is duplicated by
-
-
- Closed
-
- relates to
-
-
- Closed
-