maria-developers team mailing list archive

Thread
Date

Re: MariaDB Master Replication To MySQL

To: maria-developers@xxxxxxxxxxxxxxxxxxx
From: Kristian Nielsen <knielsen@xxxxxxxxxxxxxxx>
Date: Mon, 03 Mar 2014 10:44:22 +0100
In-reply-to: <eventum.1s15jk5n.e6rnjx@support.montyprogram.com> (Monty Program Support's message of "Mon, 3 Mar 2014 09:21:03 +0000")
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux)

> In this particular case, we have someone that wants to use MariaDB 10.0 master with a MySQL 5.6 slave. But they are running into a problem with GTID.

Generally, the recommended setup is to only replicate from old version on
master to new (or same) version on slave. Replicating from new master to old
slave in general is hard to support 100%, as there may be eg. new SQL syntax
on the master that is impossible for the old version slave to execute.

That being said, the intention is that replication from new master to old
slave (like MariaDB 10.0 -> MySQL 5.6) should work in most reasonable
cases. So this sounds like a bug which might be worth filing.

> 2.) Is it possible to disable GTID in 10.0? It seems like it would break a few other things like parallel replication, but they're only running MariaDB on the master.

GTID is disabled automatically when the slave does not support it. The code
rewrites the binlog stream on the fly to remove events that are not supported
on the old slave, and replace them with something appropriate for that slave
version.

Does the same problem occur when replicating from MariaDB 10.0 master to
MariaDB 5.5 slave? What about when replicating from MySQL 5.5 master to MySQL
5.6 slave?

 - Kristian.