File: gr_applier_thread_failure_detection.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 (89 lines) | stat: -rw-r--r-- 3,047 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
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
# This test evaluates that group replication can detect SQL thread failures of
# its applier channel.
#
# The test guide is:
# 0. A two member group with started plugins
# 1. Create a table t1 on server 1 and replicate
#    Also insert a value in the table without logging to the binlog
# 2. Insert a value on server 2 that will clash with data on server1
# 3. Check that server1 applier fails and the plugin goes to error mode.
# 4. Remove the value, restart the plugin and do a cleanup
#

--source include/big_test.inc
--source include/have_group_replication_plugin.inc
--source include/group_replication.inc

--echo #
--echo # 1. Create a table on server 1 and replicate
--echo # Also add a value in the table without logging to the binlog
--echo #

--let $rpl_connection_name= server1
--source include/rpl_connection.inc

CREATE TABLE t1 (a INT PRIMARY KEY);

SET SESSION sql_log_bin= 0;
INSERT INTO t1 VALUES (1);
SET SESSION sql_log_bin= 1;

--source include/rpl_sync.inc

--echo #
--echo # 2. Insert a value on server 2 that will clash with data on server1
--echo #

--let $rpl_connection_name= server2
--source include/rpl_connection.inc

INSERT INTO t1 VALUES (1);  # Duplicate entry

--echo #
--echo # 3. Check that server1 applier fails and the plugin goes to error mode.
--echo #

--let $rpl_connection_name= server1
--source include/rpl_connection.inc

--echo # Expect ERROR state.
--let $group_replication_member_state= ERROR
--source include/gr_wait_for_member_state.inc

--let $group_replication_number_of_members= 1
--source include/gr_wait_for_number_of_members.inc

--let $rpl_connection_name= server2
--source include/rpl_connection.inc

--echo # Wait for one member on server 2
--let $group_replication_number_of_members= 1
--source include/gr_wait_for_number_of_members.inc

--echo #
--echo # 4. Remove the value, restart the plugin and do a cleanup
--echo #

--let $rpl_connection_name= server1
--source include/rpl_connection.inc

--source include/stop_group_replication.inc

SET SESSION sql_log_bin= 0;
DELETE FROM t1 WHERE a=1;
SET SESSION sql_log_bin= 1;

--source include/start_group_replication.inc

DROP TABLE t1;

SET SESSION sql_log_bin= 0;
call mtr.add_suppression("Replica SQL for channel 'group_replication_applier': Could not execute Write_rows event on table test.t1*.*");
call mtr.add_suppression("The applier thread execution was aborted. Unable to process more transactions, this member will now leave the group.");
call mtr.add_suppression("Fatal error during execution on the Applier process of Group Replication. The server will now leave the group.");
call mtr.add_suppression("The server was automatically set into read only mode after an error was detected.");
call mtr.add_suppression("Replica SQL for channel 'group_replication_applier': Worker .* failed executing transaction .*");
call mtr.add_suppression("Replica SQL for channel 'group_replication_applier': ... The replica coordinator and worker threads are stopped,.*");
SET SESSION sql_log_bin= 1;

--source include/group_replication_end.inc