Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Fixed
-
10.0.8
-
None
Description
master:
MySQL [test]> set binlog_rows_query_log_events=ON; |
Query OK, 0 rows affected (0.00 sec) |
|
MySQL [test]> create table t1 (i int, c varchar(8)); |
Query OK, 0 rows affected (0.56 sec) |
|
MySQL [test]> insert into t1 values (1,'a'),(2,'b'); |
Query OK, 2 rows affected (0.07 sec) |
Records: 2 Duplicates: 0 Warnings: 0
|
Slave:
Last_SQL_Errno: 1594
|
Last_SQL_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 might be an unavoidable limitation, in which case it needs to be documented (as it is in MySQL docs for replicating to pre-5.6.2 slaves).
Attachments
Issue Links
- blocks
-
MDEV-5705 replication testing: 5.6->10.0
- Stalled