maria-discuss team mailing list archive
-
maria-discuss team
-
Mailing list archive
-
Message #05059
Re: Replication New to Old
-
To:
Michael Caplan <michael@xxxxxxxxxxx>
-
From:
andrei.elkin@xxxxxxxxxx
-
Date:
Thu, 05 Apr 2018 22:18:20 +0300
-
Cc:
maria-discuss@xxxxxxxxxxxxxxxxxxx
-
In-reply-to:
<aec3ba99-9944-abe1-15b3-5b0b0aa0519c@eggplant.ws> (Michael Caplan's message of "Thu, 5 Apr 2018 15:22:11 -0300")
-
Organization:
Home sweet home
-
Razorgate-kas:
Status: not_detected
-
Razorgate-kas:
Rate: 0
-
Razorgate-kas:
Envelope from:
-
Razorgate-kas:
Version: 5.5.3
-
Razorgate-kas:
LuaCore: 80 2014-11-10_18-01-23 260f8afb9361da3c7edfd3a8e3a4ca908191ad29
-
Razorgate-kas:
Lua profiles 69136 [Nov 12 2014]
-
Razorgate-kas:
Method: none
-
User-agent:
Gnus/5.13 (Gnus v5.13) Emacs/26.0.50 (gnu/linux)
Mike,
> Hello,
>
> I realize that in general replication from a newer master to an older
> slave is typically not recommended. This said, does anyone have an
> experience replicating from MariaDB 10.2 to MySQL 5.6?
A problem that is evident at once is 10.2 GTID events can not be handled
by 5.6. So at least some filtering should be devised.
To that part, maybe
mysqlbinlog --read-from-remote-server=10.2-"master" | filter | mysql-client-to 5.6-"slave"
could be practical?
>
> The compatibility matrix found here:
> https://mariadb.com/kb/en/library/mariadb-vs-mysql-compatibility/
> Seems to be missing data on this type of setup.
>
True. Cross-vendor replication check is very involving.
>
> Thanks,
>
> Mike
Cheers,
Andrei
Follow ups
References