File: rpl_show_slave_status_deadlock.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 (74 lines) | stat: -rw-r--r-- 2,704 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
###############################################################################
# Bug#19843808: DEADLOCK ON FLUSH TABLES WITH READ LOCK + SHOW
# SLAVE STATUS
#
# Problem:
# ========
# If a client thread on an slave does FLUSH TABLES WITH READ
# LOCK; then master does some updates, SHOW SLAVE STATUS in
# the same client will be blocked.
#
# Test:
# =====
# Execute a DML on master and make it blocked on slave after entering commit.
# Execute FLUSH TABLES WITH READ LOCK on slave. Allow the blocked DML to
# continue. The sql thread will be blocked in a state where it has acquired
# rli->data_lock and it is waiting for MDL COMMIT lock. Now execute show slave
# status command from the same client where FLUSH TABLES WITH READ LOCK was
# issued. The show slave status command should not be blocked.
###############################################################################
--source include/have_binlog_format_mixed.inc
--source include/master-slave.inc
--source include/have_debug.inc
--source include/have_debug_sync.inc

--echo # Let master and slave synced with t1 table created
CREATE TABLE t1 (f INT) ENGINE= INNODB;
--source include/sync_slave_sql_with_master.inc

--echo # Setup GLOBAL.DEBUG at slave to reach commit
--source include/rpl_connection_slave.inc

--let $debug_point= dbug.reached_commit
--source include/add_debug_point.inc

--echo # Do some DML operation on master so that it will be blocked on
--echo # slave as global read lock is in place.
--source include/rpl_connection_master.inc
INSERT INTO t1 VALUES (10);

--echo # Issue FLUSH TABLES WITH READ LOCK after Reached is signaled
--source include/rpl_connection_slave.inc
SET DEBUG_SYNC='now WAIT_FOR Reached';
FLUSH TABLES WITH READ LOCK;
--echo # Let sql thread continue to try to obtain commit lock
SET DEBUG_SYNC= 'now SIGNAL signal.commit_continue';

--echo # Wait until sql thread enters "Waiting for commit lock" state
let $wait_condition= SELECT COUNT(*) = 1 FROM information_schema.processlist
                     WHERE state = "Waiting for commit lock";
--source include/wait_condition.inc

--source include/rpl_connection_slave.inc
--disable_result_log
query_vertical SHOW SLAVE STATUS;
--enable_result_log
UNLOCK TABLES;

--let $debug_point= dbug.reached_commit
--source include/remove_debug_point.inc

--echo # Restart SQL thread so that it notices debug has changed
--source include/restart_slave_sql.inc

--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;

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

--source include/rpl_end.inc