[MDEV-5115] RBR from MySQL 5.6 to MariaDB 10.0 does not work Created: 2013-10-09  Updated: 2014-02-19  Resolved: 2013-12-12

Status: Closed
Project: MariaDB Server
Component/s: None
Affects Version/s: 10.0.4
Fix Version/s: 10.0.7

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Sergei Golubchik
Resolution: Fixed Votes: 0
Labels: replication

Issue Links:
Relates
relates to MDEV-5705 replication testing: 5.6->10.0 Stalled

 Description   

Row-based replication from MySQL 5.6 (tried 5.6.10 and the current tree) to MariaDB 10.0 breaks immediately with

Last_Errno: 1594
 
Last_Error: Relay log read failure: Could not parse relay log event entry. The possible reasons are: the master's binary log is corrupted (you can check this by running 'mysqlbinlog' on the binary log), the slave's relay log is corrupted (you can check this by running 'mysqlbinlog' on the relay log), a network problem, or a bug in the master's or slave's MySQL code. If you want to check the master's binary log or slave's relay log, you will be able to know their names by issuing 'SHOW SLAVE STATUS' on this slave.

It happens even if GTID is not enabled on MySQL master.
SBR seems to work. 

SET binlog_format=ROW;
 
CREATE TABLE t1 (i INT);
 
INSERT INTO t1 VALUES (1);



 Comments   
Comment by Sergei Golubchik [ 2013-10-31 ]

This fails, because we didn't merge WL#5917 from 5.6. That task has added new binlog event types, that MariaDB is not aware of.

We'll need to merge that feature.

Meanwhile, one can set log_bin_use_v1_row_events=1 as a workaround (on the master side, in MySQL-5.6, on the command line, in the my.cnf, or using the SET GLOBAL statement).

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