Debian Codegraph @

mysql-test/suite/galera/t/MDEV-29512.test

raw
1 #
2 # This test is for reproducing the issue in:
3 # https://jira.mariadb.org/browse/MDEV-29512
4 #
5 # The hanging in MDEV-29512 happens when binlog purging is attempted, and there is
6 # one local BF aborted transaction waiting for commit monitor.
7 #
8 # The test will launch two node cluster and enable binlogging with expire log days,
9 # to force binlog purging to happen.
10 # A local transaction is executed so that will become BF abort victim, and has advanced
11 # to replication stage waiting for commit monitor for final cleanup (to mark position in innodb)
12 # after that, applier is released to complete the BF abort and due to binlog configuration,
13 # starting the binlog purging. This is where the hanging would occur, if code is buggy
14 #
15 --source include/galera_cluster.inc
16 --source include/have_innodb.inc
17 --source include/have_debug_sync.inc
18 --source include/galera_have_debug_sync.inc
19
20 #
21 # binlog size is limited to 4096 bytes, we will create enough events to
22 # cause binlog rotation
23 #
24 CREATE TABLE t1 (f1 INTEGER PRIMARY KEY, f2 int, f3 varchar(2000));
25 INSERT INTO t1 VALUES (1, 0, REPEAT('1234567890', 200));
26 INSERT INTO t1 VALUES (3, 3, REPEAT('1234567890', 200));
27
28 SET SESSION wsrep_sync_wait=0;
29
30 # set sync point for replication applier
31 SET GLOBAL DEBUG_DBUG = "d,sync.wsrep_apply_cb";
32
33 # Control connection to manage sync points for appliers
34 --connect node_1a, 127.0.0.1, root, , test, $NODE_MYPORT_1
35 --connection node_1a
36 SET SESSION wsrep_sync_wait=0;
37
38 # starting local transaction, only select so far,
39 # write will happen later and this will be ordered after the transaction in node_2
40 --connection node_1
41 begin;
42 select f1,f2 from t1;
43
44 # send from node 2 an UPDATE transaction, which will BF abort the transaction in node_1
45 --connection node_2
46 --let $wait_condition=select count(*)=2 from t1
47 --source include/wait_condition.inc
48
49 UPDATE t1 SET f2=2 WHERE f1=3;
50
51 --connection node_1a
52 # wait to see the UPDATE from node_2 in apply_cb sync point
53 SET SESSION DEBUG_SYNC = "now WAIT_FOR sync.wsrep_apply_cb_reached";
54
55 --connection node_1
56 # now issuing conflicting update
57 UPDATE t1 SET f2=1 WHERE f1=3;
58
59 # Block the local commit, send final COMMIT and wait until it gets blocked
60 --let $galera_sync_point = commit_monitor_master_enter_sync
61 --source include/galera_set_sync_point.inc
62 --send COMMIT
63
64 --connection node_1a
65 # wait for the local commit to enter in commit monitor wait state
66 --let $galera_sync_point = commit_monitor_master_enter_sync
67 --source include/galera_wait_sync_point.inc
68 --source include/galera_clear_sync_point.inc
69
70 # release the local transaction to continue with commit
71 --let $galera_sync_point = commit_monitor_master_enter_sync
72 --source include/galera_signal_sync_point.inc
73
74 # and now release the applier, it should force local trx to abort
75 SET GLOBAL DEBUG_DBUG = "";
76 SET DEBUG_SYNC = "now SIGNAL signal.wsrep_apply_cb";
77 SET GLOBAL debug_dbug = NULL;
78 SET debug_sync='RESET';
79
80 --connection node_1
81 --error ER_LOCK_DEADLOCK
82 --reap
83
84 # wait until applying is complete
85 --let $wait_condition = SELECT COUNT(*)=1 FROM t1 WHERE f2=2
86 --source include/wait_condition.inc
87
88 # final read to verify what we got
89 select f1,f2 from t1;
90
91 DROP TABLE t1;