File: gr_xa_failover.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 (109 lines) | stat: -rw-r--r-- 3,875 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
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
###############################################################################
# Validate that XA transactions can be prepared on a group primary (server1)
# and committed on a different primary (server2) after a failover.
# Also validate that the old primary (server1) can rejoin the group as a
# secondary and commit the XA transaction that it did prepare.
# Both situations happen while the old primary (server1) keep the
# client session that did the XA PREPATE active.
#
# Test:
# 0. The test requires two servers: M1 and M2.
# 1. Bootstrap a group with server1 as the primary.
# 2. Join server2 to the group.
# 3. Do the XA PREPARE on the initial primary (server1)
# 4. server1 will leave the group, server2 will be elected
#    primary.
#    The client session that did the XA PREPARE will remain
#    active.
# 5. server2 is the new primary, the XA transaction will be
#    resumed on it.
#    This mimics a load balancer behavior.
# 6. server1 rejoins the group, now as a secondary, it will
#    receive the XA COMMIT through distributed recovery.
# 7. Clean up.
###############################################################################
--let $rpl_group_replication_single_primary_mode=1
--let $rpl_skip_group_replication_start= 1
--source include/have_group_replication_plugin.inc
--source include/group_replication.inc

--let $option_name = xa_detach_on_prepare
--let $option_value = 1
--source include/only_with_option.inc

--echo
--echo ############################################################
--echo # 1. Bootstrap a group with server1 as the primary.
--let $rpl_connection_name= server1
--source include/rpl_connection.inc
--source include/start_and_bootstrap_group_replication.inc
CREATE TABLE t1 (c1 INT NOT NULL PRIMARY KEY);


--echo
--echo ############################################################
--echo # 2. Join server2 to the group.
--let $rpl_connection_name= server2
--source include/rpl_connection.inc
--source include/start_group_replication.inc


--echo
--echo ############################################################
--echo # 3. Do the XA PREPARE on the initial primary (server1)
--let $rpl_connection_name= server1
--source include/rpl_connection.inc
FLUSH LOGS;
XA START '1';
INSERT INTO t1 VALUES (1);
XA END '1';
XA PREPARE '1';
--source include/rpl_sync.inc


--echo
--echo ############################################################
--echo # 4. server1 will leave the group, server2 will be elected
--echo #    primary.
--echo #    The client session that did the XA PREPARE will remain
--echo #    active.
--let $rpl_connection_name= server1
--source include/rpl_connection.inc
--source include/stop_group_replication.inc


--echo
--echo ############################################################
--echo # 5. server2 is the new primary, the XA transaction will be
--echo #    resumed on it.
--echo #    This mimics a load balancer behavior.
--let $rpl_connection_name= server2
--source include/rpl_connection.inc
XA COMMIT '1';

--let $assert_text= 'There is a value 1 in table t1'
--let $assert_cond= [SELECT COUNT(*) AS count FROM t1 WHERE t1.c1 = 1, count, 1] = 1
--source include/assert.inc


--echo
--echo ############################################################
--echo # 6. server1 rejoins the group, now as a secondary, it will
--echo #    receive the XA COMMIT through distributed recovery.
--let $rpl_connection_name= server1
--source include/rpl_connection.inc
--source include/start_group_replication.inc

--let $assert_text= 'There is a value 1 in table t1'
--let $assert_cond= [SELECT COUNT(*) AS count FROM t1 WHERE t1.c1 = 1, count, 1] = 1
--source include/assert.inc


--echo
--echo ############################################################
--echo # 7. Clean up.
--let $rpl_connection_name= server2
--source include/rpl_connection.inc
DROP TABLE t1;

--source include/group_replication_end.inc