mirror of
https://github.com/MariaDB/server.git
synced 2025-01-29 02:05:57 +01:00
cc7925765e
As a side-effect of purge_relay_logs(), sql_slave_skip_counter was silently ignored in GTID mode. But sql_slave_skip_counter in fact is not a good match with GTID. And it is not really needed either, as users can explicitly set @@gtid_slave_pos to skip specific GTIDs, in a way that matches well how GTID replication works. So with this patch, we give an error on attempts to set sql_slave_skip_counter when using GTID, with a suggestion to use gtid_slave_pos instead, if needed.
41 lines
1,010 B
Text
41 lines
1,010 B
Text
--let $rpl_topology= 1->3
|
|
--source include/rpl_init.inc
|
|
|
|
--echo *** 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 ***
|
|
|
|
--connection server_1
|
|
create table t1 (i int);
|
|
|
|
--connection server_2
|
|
create table t2 (i int);
|
|
|
|
--connection server_3
|
|
|
|
set default_master_connection = 'm2';
|
|
--replace_result $SERVER_MYPORT_2 SERVER_MYPORT_2
|
|
eval change master to master_host='127.0.0.1', master_port=$SERVER_MYPORT_2, master_user='root', master_use_gtid=slave_pos;
|
|
--source include/start_slave.inc
|
|
|
|
--connection server_2
|
|
insert into t2 values (1);
|
|
--save_master_pos
|
|
|
|
--connection server_3
|
|
--sync_with_master 0,'m2'
|
|
|
|
--connection server_1
|
|
drop table t1;
|
|
|
|
--connection server_2
|
|
drop table t2;
|
|
--save_master_pos
|
|
|
|
--connection server_3
|
|
--sync_with_master 0,'m2'
|
|
set default_master_connection = 'm2';
|
|
--source include/stop_slave.inc
|
|
RESET SLAVE ALL;
|
|
set default_master_connection = '';
|
|
|
|
--connection server_1
|
|
--source include/rpl_end.inc
|