Details
-
Type:
Bug
-
Status: Open
-
Priority:
Minor
-
Resolution: Unresolved
-
Affects Version/s: 10.1.5
-
Fix Version/s: 10.1
-
Component/s: Replication
-
Labels:
Description
When trying to replicate from 5.7.8 to 10.1.5:
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.
Also mysqlbinlog from 10.1.5 fails:
ERROR: Error in Log_event::read_log_event(): 'Found invalid event in binary log', data_len: 61, event_type: 34
From 5.7.8 mysqlbinlog output
# at 327 #150827 10:25:04 server id 5708 end_log_pos 388 Anonymous_GTID last_committed=1 sequence_number=2 SET @@SESSION.GTID_NEXT= 'ANONYMOUS'/*!*/;
mysql-5.7.8> show global variables like '%gtid%'; +----------------------------------+-------+ | Variable_name | Value | +----------------------------------+-------+ | binlog_gtid_simple_recovery | ON | | enforce_gtid_consistency | OFF | | gtid_executed | | | gtid_executed_compression_period | 1000 | | gtid_mode | OFF | | gtid_owned | | | gtid_purged | | | session_track_gtids | OFF | +----------------------------------+-------+ 8 rows in set (0.00 sec)
It would be nice if replication from 5.7.8 (w/o GTID) to 10.1 would work.
Gliffy Diagrams
Attachments
Issue Links
- is blocked by
-
MDEV-4487 FR: Allow replication from MySQL 5.6+ when GTID is enabled on the master
-
- Open
-
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
I tried slave_skip_errors=1594, but that failed. (and needs a restart
)
Also sql_slave_skip_counter=1 failed.
The only working work-around is
Maybe something like this could work?
SET GLOBAL slave_skip_event_types='34';
It would be nice if slave_skip_errors and sql_slave_skip_counter would work in this case.