Debian Codegraph @

mysql-test/suite/rpl_gtid/t/rpl_gtid_mts_replicate_same_server_id.test

raw
1 # ==== Purpose ====
2 #
3 # Verify that --replicate-same-server-id works with GTID_MODE=ON and
4 # MTS.
5 #
6 # ==== Implementation ====
7 #
8 # The main implementation is in the .opt file: it sets up master and
9 # slave with MTS enabled and with replicate-same-server-id enabled.
10 # The test case just checks that it works to replicate a couple of
11 # simple statements in this scenario. This test does not actually use
12 # the same server_id on master and slave.
13 #
14 # ==== References ====
15 #
16 # BUG#18967791 SLAVE THREAD FAILS WITH MTS + GTID + REPLICATE_SAME_SERVER_ID
17 # Prior to this bug, the MTS slave would fail when reading
18 # Previous_gtids_log_event. This only happened when
19 # replicate-same-server-id was enabled because any
20 # Previous_gtids_log_event in the relay log is generated by the
21 # slave and has the slave's server_id.
22
23 --source include/not_group_replication_plugin.inc
24 --source include/only_mts_replica_parallel_workers.inc
25 --source include/not_rpl_gtid_only.inc
26 --let $use_gtids= 0
27 --source include/master-slave.inc
28
29 CREATE TABLE t1 (a INT);
30 INSERT INTO t1 VALUES (1);
31 --source include/sync_slave_sql_with_master.inc
32
33 --let $assert_cond= a = 1 FROM t1
34 --let $assert_text= The two statements should have been replicated, so that t1 contains value 1.
35 --source include/assert.inc
36
37 --connection master
38 DROP TABLE t1;
39
40 --source include/rpl_end.inc