| 1 |
include/master-slave.inc |
| 2 |
[connection master] |
| 3 |
include/rpl_gtid_until_before_after_gtids.inc |
| 4 |
# |
| 5 |
# Test Setup (SQL_BEFORE_GTIDS) |
| 6 |
# Clean primary and replica states |
| 7 |
connection master; |
| 8 |
connection slave; |
| 9 |
connection master; |
| 10 |
RESET MASTER; |
| 11 |
set session gtid_domain_id=0; |
| 12 |
# Initialize test data |
| 13 |
connection master; |
| 14 |
create table t1 (a int); |
| 15 |
create table t2 (a int); |
| 16 |
connection slave; |
| 17 |
# |
| 18 |
# Test Case 1 (SQL_BEFORE_GTIDS): For a single-dimensional binlog state and a |
| 19 |
# STOP SLAVE UNTIL gtid position with one GTID, the replica should |
| 20 |
# execute events up until the GTID is encountered, and immediately stop |
| 21 |
connection slave; |
| 22 |
connection master; |
| 23 |
set session gtid_domain_id=0; |
| 24 |
INSERT INTO t1 VALUES (100); |
| 25 |
INSERT INTO t1 VALUES (101); |
| 26 |
INSERT INTO t1 VALUES (102); |
| 27 |
connection slave; |
| 28 |
START SLAVE UNTIL SQL_BEFORE_GTIDS="0-1-4"; |
| 29 |
# Ensure the slave started |
| 30 |
# Clean replica state |
| 31 |
connection master; |
| 32 |
connection slave; |
| 33 |
# |
| 34 |
# Test Case 2 (SQL_BEFORE_GTIDS): If a provided until GTID doesn't exist in the |
| 35 |
# binary log due to a gap, once an event is seen that is beyond the |
| 36 |
# until GTID, the slave should immediately stop. Note the behavior of |
| 37 |
# this test case should be the same between SQL_BEFORE_GTIDS and |
| 38 |
# SQL_AFTER_GTIDS. |
| 39 |
connection slave; |
| 40 |
connection master; |
| 41 |
set session gtid_domain_id=0; |
| 42 |
INSERT INTO t1 VALUES (103); |
| 43 |
INSERT INTO t1 VALUES (104); |
| 44 |
# Skip a seq_no |
| 45 |
set @@session.gtid_seq_no= 9; |
| 46 |
INSERT INTO t1 VALUES (105); |
| 47 |
connection slave; |
| 48 |
START SLAVE UNTIL SQL_BEFORE_GTIDS="0-1-8"; |
| 49 |
# Ensure the slave started |
| 50 |
connection slave; |
| 51 |
connection master; |
| 52 |
connection slave; |
| 53 |
# |
| 54 |
# Test Case 3 (SQL_BEFORE_GTIDS): For a multi-dimensional binlog state and a |
| 55 |
# STOP SLAVE UNTIL gtid position with one GTID, the replica should |
| 56 |
# execute events from only the specified domain until the provided GTID |
| 57 |
# is encountered, and immediately stop |
| 58 |
connection slave; |
| 59 |
connection master; |
| 60 |
set session gtid_domain_id=0; |
| 61 |
INSERT INTO t1 VALUES (106); |
| 62 |
set session gtid_domain_id=1; |
| 63 |
INSERT INTO t2 VALUES (200); |
| 64 |
INSERT INTO t2 VALUES (201); |
| 65 |
set session gtid_domain_id=0; |
| 66 |
INSERT INTO t1 VALUES (107); |
| 67 |
set session gtid_domain_id=1; |
| 68 |
INSERT INTO t2 VALUES (202); |
| 69 |
set session gtid_domain_id=0; |
| 70 |
connection slave; |
| 71 |
START SLAVE UNTIL SQL_BEFORE_GTIDS="0-1-11"; |
| 72 |
# Ensure the slave started |
| 73 |
connection slave; |
| 74 |
connection master; |
| 75 |
connection slave; |
| 76 |
# |
| 77 |
# Test Case 4 (SQL_BEFORE_GTIDS): For a multi-dimensional binlog state and a |
| 78 |
# STOP SLAVE UNTIL gtid position with multiple GTIDs, the replica should |
| 79 |
# for each domain, execute events only up until its provided GTID, and |
| 80 |
# once all domains have hit their end point, immediately stop. |
| 81 |
connection slave; |
| 82 |
connection master; |
| 83 |
SET STATEMENT gtid_domain_id=0 FOR INSERT INTO t1 VALUES (108); |
| 84 |
# Tagging domain 0 stop: 0-1-12 |
| 85 |
SET STATEMENT gtid_domain_id=0 FOR INSERT INTO t1 VALUES (109); |
| 86 |
SET STATEMENT gtid_domain_id=1 FOR INSERT INTO t2 VALUES (203); |
| 87 |
SET STATEMENT gtid_domain_id=1 FOR INSERT INTO t2 VALUES (204); |
| 88 |
SET STATEMENT gtid_domain_id=0 FOR INSERT INTO t1 VALUES (110); |
| 89 |
SET STATEMENT gtid_domain_id=1 FOR INSERT INTO t2 VALUES (205); |
| 90 |
connection slave; |
| 91 |
START SLAVE UNTIL SQL_BEFORE_GTIDS="0-1-13,1-1-5"; |
| 92 |
# Ensure the slave started |
| 93 |
connection slave; |
| 94 |
connection master; |
| 95 |
connection slave; |
| 96 |
# |
| 97 |
# Error Case 1: Not providing a valid GTID should result in a syntax |
| 98 |
# error |
| 99 |
connection slave; |
| 100 |
START SLAVE UNTIL SQL_BEFORE_GTIDS="a"; |
| 101 |
ERROR HY000: Could not parse GTID list |
| 102 |
START SLAVE UNTIL SQL_BEFORE_GTIDS="0"; |
| 103 |
ERROR HY000: Could not parse GTID list |
| 104 |
START SLAVE UNTIL SQL_BEFORE_GTIDS="0-1"; |
| 105 |
ERROR HY000: Could not parse GTID list |
| 106 |
START SLAVE UNTIL SQL_BEFORE_GTIDS="0-1-"; |
| 107 |
ERROR HY000: Could not parse GTID list |
| 108 |
START SLAVE UNTIL SQL_BEFORE_GTIDS="a-b-c"; |
| 109 |
ERROR HY000: Could not parse GTID list |
| 110 |
# |
| 111 |
# Cleanup test data |
| 112 |
connection master; |
| 113 |
DROP TABLE t1, t2; |
| 114 |
connection slave; |
| 115 |
include/rpl_gtid_until_before_after_gtids.inc |
| 116 |
# |
| 117 |
# Test Setup (SQL_AFTER_GTIDS) |
| 118 |
# Clean primary and replica states |
| 119 |
connection master; |
| 120 |
connection slave; |
| 121 |
connection master; |
| 122 |
RESET MASTER; |
| 123 |
set session gtid_domain_id=0; |
| 124 |
# Initialize test data |
| 125 |
connection master; |
| 126 |
create table t1 (a int); |
| 127 |
create table t2 (a int); |
| 128 |
connection slave; |
| 129 |
# |
| 130 |
# Test Case 1 (SQL_AFTER_GTIDS): For a single-dimensional binlog state and a |
| 131 |
# STOP SLAVE UNTIL gtid position with one GTID, the replica should |
| 132 |
# execute events up until the GTID is encountered, finish replicating |
| 133 |
# that event group, and then stop |
| 134 |
connection slave; |
| 135 |
connection master; |
| 136 |
set session gtid_domain_id=0; |
| 137 |
INSERT INTO t1 VALUES (111); |
| 138 |
INSERT INTO t1 VALUES (112); |
| 139 |
INSERT INTO t1 VALUES (113); |
| 140 |
connection slave; |
| 141 |
START SLAVE UNTIL SQL_AFTER_GTIDS="0-1-4"; |
| 142 |
# Ensure the slave started |
| 143 |
# Clean replica state |
| 144 |
connection master; |
| 145 |
connection slave; |
| 146 |
# |
| 147 |
# Test Case 2 (SQL_AFTER_GTIDS): If a provided until GTID doesn't exist in the |
| 148 |
# binary log due to a gap, once an event is seen that is beyond the |
| 149 |
# until GTID, the slave should immediately stop. Note the behavior of |
| 150 |
# this test case should be the same between SQL_BEFORE_GTIDS and |
| 151 |
# SQL_AFTER_GTIDS. |
| 152 |
connection slave; |
| 153 |
connection master; |
| 154 |
set session gtid_domain_id=0; |
| 155 |
INSERT INTO t1 VALUES (114); |
| 156 |
INSERT INTO t1 VALUES (115); |
| 157 |
# Skip a seq_no |
| 158 |
set @@session.gtid_seq_no= 9; |
| 159 |
INSERT INTO t1 VALUES (116); |
| 160 |
connection slave; |
| 161 |
START SLAVE UNTIL SQL_AFTER_GTIDS="0-1-8"; |
| 162 |
# Ensure the slave started |
| 163 |
connection slave; |
| 164 |
connection master; |
| 165 |
connection slave; |
| 166 |
# |
| 167 |
# Test Case 3 (SQL_AFTER_GTIDS): For a multi-dimensional binlog state and a |
| 168 |
# STOP SLAVE UNTIL gtid position with one GTID, the replica should |
| 169 |
# execute events from only the specified domain until the provided GTID |
| 170 |
# is encountered, finish replicating that event group, and then stop |
| 171 |
connection slave; |
| 172 |
connection master; |
| 173 |
set session gtid_domain_id=0; |
| 174 |
INSERT INTO t1 VALUES (117); |
| 175 |
set session gtid_domain_id=1; |
| 176 |
INSERT INTO t2 VALUES (206); |
| 177 |
INSERT INTO t2 VALUES (207); |
| 178 |
set session gtid_domain_id=0; |
| 179 |
INSERT INTO t1 VALUES (118); |
| 180 |
set session gtid_domain_id=1; |
| 181 |
INSERT INTO t2 VALUES (208); |
| 182 |
set session gtid_domain_id=0; |
| 183 |
connection slave; |
| 184 |
START SLAVE UNTIL SQL_AFTER_GTIDS="0-1-11"; |
| 185 |
# Ensure the slave started |
| 186 |
connection slave; |
| 187 |
connection master; |
| 188 |
connection slave; |
| 189 |
# |
| 190 |
# Test Case 4 (SQL_AFTER_GTIDS): For a multi-dimensional binlog state and a |
| 191 |
# STOP SLAVE UNTIL gtid position with multiple GTIDs, the replica should |
| 192 |
# stop executing events as soon as all listed GTIDs in the UNTIL list |
| 193 |
# have been executed. |
| 194 |
connection slave; |
| 195 |
connection master; |
| 196 |
SET STATEMENT gtid_domain_id=0 FOR INSERT INTO t1 VALUES (119); |
| 197 |
SET STATEMENT gtid_domain_id=0 FOR INSERT INTO t1 VALUES (120); |
| 198 |
SET STATEMENT gtid_domain_id=1 FOR INSERT INTO t2 VALUES (209); |
| 199 |
SET STATEMENT gtid_domain_id=1 FOR INSERT INTO t2 VALUES (210); |
| 200 |
SET STATEMENT gtid_domain_id=0 FOR INSERT INTO t1 VALUES (121); |
| 201 |
SET STATEMENT gtid_domain_id=1 FOR INSERT INTO t2 VALUES (211); |
| 202 |
connection slave; |
| 203 |
START SLAVE UNTIL SQL_AFTER_GTIDS="0-1-13,1-1-5"; |
| 204 |
# Ensure the slave started |
| 205 |
connection slave; |
| 206 |
connection master; |
| 207 |
connection slave; |
| 208 |
# |
| 209 |
# Error Case 1: Not providing a valid GTID should result in a syntax |
| 210 |
# error |
| 211 |
connection slave; |
| 212 |
START SLAVE UNTIL SQL_AFTER_GTIDS="a"; |
| 213 |
ERROR HY000: Could not parse GTID list |
| 214 |
START SLAVE UNTIL SQL_AFTER_GTIDS="0"; |
| 215 |
ERROR HY000: Could not parse GTID list |
| 216 |
START SLAVE UNTIL SQL_AFTER_GTIDS="0-1"; |
| 217 |
ERROR HY000: Could not parse GTID list |
| 218 |
START SLAVE UNTIL SQL_AFTER_GTIDS="0-1-"; |
| 219 |
ERROR HY000: Could not parse GTID list |
| 220 |
START SLAVE UNTIL SQL_AFTER_GTIDS="a-b-c"; |
| 221 |
ERROR HY000: Could not parse GTID list |
| 222 |
# |
| 223 |
# Cleanup test data |
| 224 |
connection master; |
| 225 |
DROP TABLE t1, t2; |
| 226 |
connection slave; |
| 227 |
# |
| 228 |
# Error Case 2: Providing both SQL_BEFORE_GTIDS and SQL_AFTER_GTIDS |
| 229 |
# should result in a syntax error |
| 230 |
connection slave; |
| 231 |
START SLAVE UNTIL SQL_AFTER_GTIDS="0-1-1" SQL_BEFORE_GTIDS="0-1-1"; |
| 232 |
ERROR 42000: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'SQL_BEFORE_GTIDS="0-1-1"' at line 1 |
| 233 |
# |
| 234 |
# Cleanup |
| 235 |
include/save_master_gtid.inc |
| 236 |
connection slave; |
| 237 |
include/sync_with_master_gtid.inc |
| 238 |
include/rpl_end.inc |
| 239 |
# End of rpl_gtid_until_before_gtids.test |