[MDEV-5705] replication testing: 5.6->10.0 Created: 2014-02-19  Updated: 2022-09-08

Status: Stalled
Project: MariaDB Server
Component/s: None
Fix Version/s: None

Type: Task Priority: Minor
Reporter: Sergei Golubchik Assignee: Alice Sherepa
Resolution: Unresolved Votes: 0
Labels: None

Issue Links:
Blocks
is blocked by MDEV-4487 FR: Allow replication from MySQL 5.6+... Closed
is blocked by MDEV-5765 Replication 5.6=>10.0 causes garbage ... Open
is blocked by MDEV-5767 Replication 5.6=>10.0 fails with binl... Closed
Relates
relates to MDEV-5769 Slave crashes on attempt to do parall... Closed
relates to MDEV-5785 RBR between old master and new slave ... Closed
relates to MDEV-5799 Error messages written upon LOST EVEN... Closed
relates to MDEV-3823 Backport WL#5917 sufficient to be abl... Closed
relates to MDEV-5115 RBR from MySQL 5.6 to MariaDB 10.0 do... Closed

 Description   

We need to test to what extent replication from 5.6 to 10.0 works. That is what new replication features in 5.6 are understood by 10.0 and what aren't.

These new replication features are at least:

  • New insert/update/delete row events (MDEV-5115)
  • event checksums (already in 5.2, backported from 5.6)
  • ignorable events (fixed as part of MDEV-4487)
  • global transaction id (ignored with MDEV-4487)

the list above is not exhaustive.

 Comments   
Comment by Elena Stepanova [ 2014-03-09 ]

The current status is that replication 5.6 => 10.0.9 works to some extent – if the master is not using non-default replication- modes or configuration, e.g. GTID, binlog_row_image and such.
This replication path can be used as an upgrade mechanism, if during the upgrade window the master does not write into the binary log any new syntax not merged into 10.0.

Related bugs can be found in "Issue links".

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