Debian Codegraph @

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

raw
1 # ==== Purpose ====
2 #
3 # This test will check if reset slave is generating correct Previous_gtids
4 # event in first relay log file after a RESET SLAVE.
5 #
6 # It will:
7 # 1) generate some workload at the master;
8 # 2) sync the slave with the master;
9 # 3) stop slave replication threads;
10 # 4) do RESET MASTER on the master;
11 # 5) do RESET MASTER on the slave;
12 # 6) do RESET SLAVE on the slave;
13 # 7) restart the slave.
14 #
15 # Slave shall be able to sync with master without issues.
16 #
17 # ==== Related Bugs and Worklogs ====
18 #
19 # BUG#27636289 RPL BREAKS WITH RESTART AFTER RESET SLAVE IF --RELAY-LOG-PURGE=0
20 #
21
22 # This test case is binary log format agnostic
23 --source include/have_binlog_format_row.inc
24 --source include/master-slave.inc
25
26 CREATE TABLE t1 (c1 INT);
27 --source include/sync_slave_sql_with_master.inc
28 --source include/stop_slave.inc
29
30 --source include/rpl_connection_master.inc
31 RESET MASTER;
32
33 --source include/rpl_connection_slave.inc
34 RESET MASTER;
35 RESET SLAVE;
36 --source include/start_slave.inc
37
38 --source include/kill_and_restart_mysqld.inc
39
40 --let $rpl_server_number= 2
41 --source include/rpl_reconnect.inc
42
43 --source include/rpl_connection_master.inc
44 DROP TABLE t1;
45
46 --source include/rpl_end.inc