Replication Compatibility Between MariaDB and MySQL

This page describes replication compatibility between MariaDB and MySQL. For replication compatibility details between different MariaDB versions, see .

Replication Compatibility

compatibility depends on:

• The MariaDB version

• The MySQL version

• The role of each server

Replicating from MySQL to MariaDB

MySQL 5.7 to MariaDB

and later can replicate from a MySQL 5.7 primary server.

MariaDB does not support the MySQL implementation of Global Transaction IDs (GTIDs), so the MariaDB replica server must use the binary log file and position for replication. If GTID mode is enabled on the MySQL primary server, the MariaDB replica server will remove the MySQL GTID events and replace them with MariaDB GTID events.

You can disable GTID and use logfile name and position in MariaDB by executing on the slave:

Although MariaDB and MySQL 5.7 are compatible at the replication level, they may have some incompatibilities at the SQL level. Those differences can cause replication failures in some cases. To decrease the risk of compatibility issues, it is recommended to set to ROW in MySQL. When you want to replicate from MySQL 5.7 to MariaDB, it is recommended to test your application, so that any compatibility issues can be found and fixed. See between the specific versions.

MySQL 8.0 to MariaDB

Prior to , , and , MariaDB Server could not replicate from a MySQL 8.0 primary server, because MySQL 8.0 has a binary log format that includes new events which makes it incompatible.

, , , and newer can replicate from a MySQL 8.0 server with the following conditions:

• Prior to , and , MariaDB does not support the MySQL default authentication caching_sha2_password, so one has to add another replication user using the mysql_native_password protocol and use this with in MariaDB when using an older version.

• Columns of type JSON are not supported. One should change these to TEXT in MySQL. MySQL will work fine with JSON as TEXT, except for a minor performance degradation when using JSON expressions.

• binlog-row-value-options

Here are the changes one should do in the config files for MySQL 8.0:

Replicating from MariaDB to MySQL

Here are some issues to be aware of when replicating from MariaDB to MySQL.

On the MySQL side, one should:

• Not use binlog with (CHANGE SOURCE_AUTO_POSITION=no)

On the MariaDB side, one should:

• Not use ( should be 0)

• Not use ( should be 0)

• Ensure that one uses a and that MySQL supports. The MariaDB default collations for utf8mb4 is not supported by MySQL. Note that if you just have upgraded from MySQL to MariaDB then you are probably already using the MySQL character sets and collations for your old tables! If you want replication to also work for new tables, the best option is to set the character set and collation in the MariaDB config file.

Example of changes to add to the MariaDB config file:

For differences at the SQL level that may cause replication failures, see between the specific versions.

See also

_{This page is licensed: CC BY-SA / Gnu FDL}