File: rpl_reset_restart.test

package info (click to toggle)
mysql-8.0 8.0.43-3
  • links: PTS, VCS
  • area: main
  • in suites: sid
  • size: 1,273,924 kB
  • sloc: cpp: 4,684,605; ansic: 412,450; pascal: 108,398; java: 83,641; perl: 30,221; cs: 27,067; sql: 26,594; sh: 24,181; python: 21,816; yacc: 17,169; php: 11,522; xml: 7,388; javascript: 7,076; makefile: 2,194; lex: 1,075; awk: 670; asm: 520; objc: 183; ruby: 97; lisp: 86
file content (46 lines) | stat: -rw-r--r-- 1,186 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
# ==== Purpose ====
#
# This test will check if reset slave is generating correct Previous_gtids
# event in first relay log file after a RESET SLAVE.
#
# It will:
# 1) generate some workload at the master;
# 2) sync the slave with the master;
# 3) stop slave replication threads;
# 4) do RESET MASTER on the master;
# 5) do RESET MASTER on the slave;
# 6) do RESET SLAVE on the slave;
# 7) restart the slave.
#
# Slave shall be able to sync with master without issues.
#
# ==== Related Bugs and Worklogs ====
#
# BUG#27636289 RPL BREAKS WITH RESTART AFTER RESET SLAVE IF --RELAY-LOG-PURGE=0
#

# This test case is binary log format agnostic
--source include/have_binlog_format_row.inc
--source include/master-slave.inc

CREATE TABLE t1 (c1 INT);
--source include/sync_slave_sql_with_master.inc
--source include/stop_slave.inc

--source include/rpl_connection_master.inc
RESET MASTER;

--source include/rpl_connection_slave.inc
RESET MASTER;
RESET SLAVE;
--source include/start_slave.inc

--source include/kill_and_restart_mysqld.inc

--let $rpl_server_number= 2
--source include/rpl_reconnect.inc

--source include/rpl_connection_master.inc
DROP TABLE t1;

--source include/rpl_end.inc