[MDEV-10746] Replicate Data from 10.0 -> 10.1 (Corrupted replication event was detected ) Created: 2016-09-05  Updated: 2017-05-20  Resolved: 2016-09-20

Status: Closed
Project: MariaDB Server
Component/s: Replication
Affects Version/s: 10.1.11
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Maximiliano Dumon Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Environment:

Ubuntu 12.0 - Master MariaDB 10.0.20 - Slave MariaDB 10.1.11


Issue Links:
Duplicate
is duplicated by MDEV-5377 Row-based replication of MariaDB temp... Closed

 Description   

We have configured a Master (MariaDB 10.0.20) and Slave (MariaDB 10.1.11).

We have an error in the Slave:
Last_SQL_Error: Could not execute Write_rows_v1 event on table xxxxxx.xxxxxx; Unknown error, Error_code: 1105; handler error No Error!; the event's master log mysql-bin.xxxx, end_log_pos xxxxxxx

When we search the Binary Log and Position on the Maste we found this error:
"Corrupted replication event was detected. Not printing the value"

This error doesn't have problem if the replication is from MariaDB 10.0.20 to MariaDB 10.0.20.

Somebody can help us with this problem. I found many diferents issues:
https://mariadb.atlassian.net/browse/MDEV-8426-- We configured the variable binlog_row_image=FULL

Thanks in advance!

 Comments   
Comment by Elena Stepanova [ 2016-09-07 ]

Please check if MDEV-5377 is relevant to your case.

Comment by Maximiliano Dumon [ 2016-09-19 ]

We found the problem with datetime data type and binary log row format.

Thanks for all your help.
Regards.
MD

Comment by Elena Stepanova [ 2016-09-19 ]

Just to clarify – do you mean that the problem is the same as MDEV-5377, or that you found a different problem?

Comment by Maximiliano Dumon [ 2016-09-20 ]

Yes, that was the problem. Thanks for help!

Comment by Elena Stepanova [ 2016-09-20 ]

Closing as a duplicate of MDEV-5377.

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