From 69178318a7d839f1168e5565a4b4e495babf8e56 Mon Sep 17 00:00:00 2001 From: MassimilianoPinto Date: Tue, 31 Oct 2017 12:34:55 +0100 Subject: [PATCH] MXS-1487: MySQL 5.7 documentation update. MySQL 5.7 documentation update. --- .../Replication-Proxy-Binlog-Router-Tutorial.md | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/Documentation/Tutorials/Replication-Proxy-Binlog-Router-Tutorial.md b/Documentation/Tutorials/Replication-Proxy-Binlog-Router-Tutorial.md index 08cb36b53..9fd30cf7d 100644 --- a/Documentation/Tutorials/Replication-Proxy-Binlog-Router-Tutorial.md +++ b/Documentation/Tutorials/Replication-Proxy-Binlog-Router-Tutorial.md @@ -236,14 +236,19 @@ Master_SSL_Verify_Server_Cert: No # Binlog router compatibility -Binlog Router Plugin is compatible with MariaDB 5.5 and MySQL 5.6, the current default. +Binlog Router Plugin is compatible with MariaDB 5.5 and MySQL 5.6/5.7. -In order to use it with MySQL 5.6, the *GTID_MODE* setting must be OFF and connecting slaves must not use *MASTER_AUTO_POSITION = 1* option. +In order to use it with MySQL 5.6/5.7, the *GTID_MODE* setting must be OFF +and connecting slaves must not use *MASTER_AUTO_POSITION = 1* option. +Additionally with MySQL 5.7 slaves the `send_slave_heartbeat` option must be set to on. -It’s also works with a MariaDB 10.0 setup (master and slaves) but slave connection must not include any GTID feature. +It’s also works with a MariaDB 10.X setup (master and slaves). +Slave connection must not include any GTID feature if MaxScale version is less than 2.2. Binlog Router currently does not work for MySQL 5.5 due to missing *@@global.binlog_checksum* variable. +The default compatibility is MariaDB 10 since MaxScale 2.2. + # Master server setup/change In the MariaDB MaxScale ini file the server section for master is no longer required, same for *servers=master_server* in the service section. The master server setup is currently managed via *CHANGE MASTER TO* command issued in MySQL client connection to MariaDB MaxScale or by providing a proper *master.ini* file in the *binlogdir*.