mariadb/mysql-test/suite/rpl/t/rpl_gtid_mdev4485.cnf at 89e0514150433eeb9737e3bb6272b88dd82b8443 - mirror/mariadb - May the force be without you: git.fucktheforce.de

mirror/mariadb

mirror of https://github.com/MariaDB/server.git synced 2025-01-19 21:42:35 +01:00

unknown 385780f571 MDEV-4485: Master did not allow slave to connect from the very start (empty GTID pos) if GTIDs from other multi_source master was present

The idea in the code was to protect the user that tries to connect a slave
to a master with completely different domains than what was intended. If
none of the domains in the start position are present at all in the master
binlog, we gave an error.

However, this is a stupid idea. Because when a slave connects to a master
to start replication from the very start of binlogs - such as when setting
up new master->slave servers from scratch - there will be just this
situation, the requested slave position is empty for all the domains in the
master's binlog.

So the code that gives this error is wrong, and the solution is simply to
remove it.

2013-05-29 11:41:25 +02:00

18 lines

319 B

INI

Raw Blame History

 !include suite/rpl/rpl_1slave_base.cnf
 !include include/default_client.cnf
 [mysqld.1]
 log-slave-updates
 gtid-domain-id=1
 [mysqld.2]
 log-slave-updates
 gtid-domain-id=2
 [mysqld.3]
 log-slave-updates
 gtid-domain-id=3
 [ENV]
 SERVER_MYPORT_3=                @mysqld.3.port
 SERVER_MYSOCK_3=                @mysqld.3.socket