File: rpl_mts_slave_hang_with_partial_trx.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 (84 lines) | stat: -rw-r--r-- 2,829 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
# ==== Purpose ====
#
# Verify if the MTS SQL thread will became unresponsive after the slave
# applied a partial transaction (without the XID event) followed by a
# ROTATE event caused by IO thread reconnection when GTIDs and auto
# positioning are enabled.
#
# ==== Related Bugs and Worklogs ====
#
# BUG#17326020 ASSERTION ON SLAVE AFTER STOP/START SLAVE USING MTS+GTID
#              REPLICATION
# BUG#18885916 RELAY LOG WITHOUT XID_LOG_EVENT MAY CASE PARALLEL
#              REPLICATION HANG
#
# ==== Implementation ====
#
# This test uses debug points on the slave to make the
# IO thread to stop right after queuing a WRITE_ROWS log event.
#
# By doing this, the relay log file with the partial transaction
# will contain: [GTID,] QUERY(BEGIN), TABLE_MAP and WRITE_ROWS, but
# won't have the XID for the transaction.
#
# After reconnecting to the master, if the slave is configured with
# GTID and auto positioning, the IO thread will request the whole
# transaction again.
#
# The test case will then sync the slave with the master and verify
# that all data was correctly applied on slave.
#

# this test relies on a debug point that is triggered after
# the IO thread encounters a write rows log event. This is
# impossible with compression, since the IO thread will not
# parse transaction payload events
--source include/not_binlog_transaction_compression_on.inc

--source include/not_group_replication_plugin.inc
# This test case uses a debug point based on RBR
--source include/have_binlog_format_row.inc
--source include/have_debug.inc
--source include/master-slave.inc

--source include/rpl_connection_slave.inc
# Prepare the slave IO thread to stop after queuing a WRITE_ROWS event
SET @save_debug=@@global.debug;
SET GLOBAL DEBUG= "+d,stop_io_after_reading_write_rows_log_event";

# Put some data in to the master
--source include/rpl_connection_master.inc
CREATE TABLE t1 (c1 INT) ENGINE=InnoDB;
# This transaction will be split
BEGIN;
INSERT INTO t1 (c1) VALUES (1);
COMMIT;
# This transaction will not be split
BEGIN;
INSERT INTO t1 (c1) VALUES (2);
COMMIT;

# Wait the slave IO thread to reach the debug point
--source include/rpl_connection_slave.inc
--source include/wait_for_slave_io_to_stop.inc
# Remove the debug point, so the IO thread will not stop after
# queuing a WRITE_ROWS event anymore
SET GLOBAL DEBUG= @save_debug;

# Restart slave I/O thread
--source include/start_slave_io.inc

# Sync the slave with the master
--source include/rpl_connection_master.inc
--source include/sync_slave_sql_with_master.inc

# Final data verification
--source include/rpl_connection_master.inc
--source include/sync_slave_sql_with_master.inc
--let diff_tables= master:t1, slave:t1
--source include/diff_tables.inc

# Cleanup
--source include/rpl_connection_master.inc
DROP TABLE t1;
--source include/rpl_end.inc