Comments on: When you cannot replicate from master M to slave S https://shlomi-noach.github.io/blog/mysql/when-you-cannot-replicate-from-master-m-to-slave-s Blog by Shlomi Noach Fri, 13 Jun 2014 15:28:52 +0000 hourly 1 https://wordpress.org/?v=5.3.3 By: shlomi https://shlomi-noach.github.io/blog/mysql/when-you-cannot-replicate-from-master-m-to-slave-s/comment-page-1#comment-245021 Fri, 13 Jun 2014 15:28:52 +0000 https://shlomi-noach.github.io/blog/?p=6855#comment-245021 If your master has ROW format, and your slave has log_slave_updates but uses STATEMENT format, it will refuse to replicate, since it can’t translate ROW back to STATEMENT. STATEMENT to ROW is fine. STATEMENT to MIXED is fine. MIXED to ROW is fine. ROW to MIXED is disallowed.

]]> By: Ankit https://shlomi-noach.github.io/blog/mysql/when-you-cannot-replicate-from-master-m-to-slave-s/comment-page-1#comment-244965 Fri, 13 Jun 2014 06:30:28 +0000 https://shlomi-noach.github.io/blog/?p=6855#comment-244965 Can you explain the point:

–S has log_bin & log_slave_updates, uses MIXED binlog_format, and M uses ROW binlog_format

Slave being on Mixed mode should accept either format? Why should Master be not ROW binlog_format?

]]> By: Daniël van Eeden https://shlomi-noach.github.io/blog/mysql/when-you-cannot-replicate-from-master-m-to-slave-s/comment-page-1#comment-239556 Sun, 04 May 2014 19:12:01 +0000 https://shlomi-noach.github.io/blog/?p=6855#comment-239556 Binlog checksums will break replication from 5.6 to 5.5 and the same might be true for binlog-rows-query-log-events. See also http://bugs.mysql.com/bug.php?id=72522

And some non-config issues:
Non-upgraded timestamps can be an issue.
http://bugs.mysql.com/bug.php?id=70124

And a different set of storage engines between the slave and server can also cause some issues.

And if SSL is used there can be issues if one is using OpenSSL and the other is using YaSSL. And in the same category are all related ‘client’ issues like support for the authentication plugin etc.

]]> By: Jean-François Gagné https://shlomi-noach.github.io/blog/mysql/when-you-cannot-replicate-from-master-m-to-slave-s/comment-page-1#comment-239083 Tue, 29 Apr 2014 06:20:21 +0000 https://shlomi-noach.github.io/blog/?p=6855#comment-239083 M is GTID_MODE=ON and S is GTID_MODE=OFF (or the other way around).

]]> By: Mark Leith https://shlomi-noach.github.io/blog/mysql/when-you-cannot-replicate-from-master-m-to-slave-s/comment-page-1#comment-239028 Mon, 28 Apr 2014 19:08:30 +0000 https://shlomi-noach.github.io/blog/?p=6855#comment-239028 In 5.6+ you should also ensure each instance has a unique server_uuid (auto.cnf in datadir, FS clones can sometimes copy it), especially with GTID enabled instances.

]]> By: shlomi https://shlomi-noach.github.io/blog/mysql/when-you-cannot-replicate-from-master-m-to-slave-s/comment-page-1#comment-238977 Mon, 28 Apr 2014 10:07:37 +0000 https://shlomi-noach.github.io/blog/?p=6855#comment-238977 Thanks both; the above discusses configuration issues, and not a general replication HOWTO. It is of interest when moving slaves across the replication topology.

Firewall/network are all valid and quite outside the scope of this post 🙂

]]> By: Abdel-Mawla https://shlomi-noach.github.io/blog/mysql/when-you-cannot-replicate-from-master-m-to-slave-s/comment-page-1#comment-238975 Mon, 28 Apr 2014 09:53:06 +0000 https://shlomi-noach.github.io/blog/?p=6855#comment-238975 Hi,

If you are talking about general conditions where you can not establish the replication, what about firewall restrictions or slave MySQL user privileges problem ?

]]> By: Richard Bensley https://shlomi-noach.github.io/blog/mysql/when-you-cannot-replicate-from-master-m-to-slave-s/comment-page-1#comment-238969 Mon, 28 Apr 2014 08:50:35 +0000 https://shlomi-noach.github.io/blog/?p=6855#comment-238969 Ensure the user account setup for replication has the ‘REPLICATION SLAVE’ privilege for fetching events from M.

It is often mistaken with ‘REPLICATION CLIENT’ which is only used for ‘SHOW MASTER STATUS’ and ‘SHOW SLAVE STATUS’.

]]>