File: binlog_recover_async_rollback_trx.test

package info (click to toggle)
mariadb 1%3A11.8.3-1
  • links: PTS, VCS
  • area: main
  • in suites: sid
  • size: 772,520 kB
  • sloc: ansic: 2,414,714; cpp: 1,791,394; asm: 381,336; perl: 62,905; sh: 49,647; pascal: 40,897; java: 39,363; python: 20,791; yacc: 20,432; sql: 17,907; xml: 12,344; ruby: 8,544; cs: 6,542; makefile: 6,145; ada: 1,879; lex: 1,193; javascript: 996; objc: 80; tcl: 73; awk: 46; php: 22
file content (117 lines) | stat: -rw-r--r-- 4,275 bytes parent folder | download | duplicates (2)
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
110
111
112
113
114
115
116
117
################################################################################
# Async rollback prepared transactions during binlog crash recovery
#
# It verifies that binlog recovery just set the prepared transactions to
# active and the background recovery rollback thread will rollback the
# transactions asynchronously.
################################################################################
--source include/have_debug.inc
--source include/have_debug_sync.inc
--source include/have_innodb.inc
--source include/have_binlog_format_row.inc
--source include/have_sequence.inc

CREATE TABLE t1 (id int primary key, data int) ENGINE = InnoDB;
INSERT INTO t1 VALUES (0, 1);

--echo #
--echo # 1. Check DML in prepared state can rollback correctly.
--echo #

--connect(con1, localhost, root,,)
SET debug_sync = "ha_commit_trans_after_prepare SIGNAL prepared1 WAIT_FOR continue";
--send INSERT INTO t1 VALUES(1, 1);

--connect(con2, localhost, root,,)
SET debug_sync = "now WAIT_FOR prepared1";
SET debug_sync = "ha_commit_trans_after_prepare SIGNAL prepared2 WAIT_FOR continue";
--send UPDATE t1 SET data = data + 1 WHERE id = 0

--connection default
SET debug_sync = "now WAIT_FOR prepared2";
--source include/kill_mysqld.inc

--disconnect con1
--disconnect con2

# With the debug option, recovery rollback thread just rolls back the
# first prepared transaction and then goes to sleep.
--source include/start_mysqld.inc
--let $wait_condition= SELECT count(*) = 0 FROM information_schema.innodb_trx
--source include/wait_condition.inc

--echo # Expect (0, 1)
SET SESSION TRANSACTION ISOLATION LEVEL READ UNCOMMITTED;
SELECT * FROM t1;

# The previous INSERT is rolled back, so this INSERT will succeed.
INSERT INTO t1 VALUES(1, 1);

# The previous UPDATE is rolled back, so this UPDATE will succeed.
UPDATE t1 SET data = data + 1 WHERE id = 0;

--echo # Expect (0, 2), (1, 1)
SELECT * FROM t1;

--echo #
--echo # 2. Test that innodb shutdown as expected if any error happens before
--echo #    normal rollback task is started. In the situation, rollback task
--echo #    should be started at preshutdown accordingly to rollback or
--echo #    deregister all recovered active transactions.
--echo #
# Generate an large active transaction
INSERT INTO t1 SELECT seq + 2, 1 FROM seq_1_to_1024;

BEGIN;
UPDATE t1 SET data = 10;

# Make sure above update is persisted.
SET GLOBAL innodb_log_checkpoint_now = 1;
--source include/kill_mysqld.inc

# tc-heuristic-recover triggers an error before innodb rollback task start
# Rollback task will not be started at preshutdown of read only mode. Active
# transactions are not expected to rollback.
--error 1
--exec $MYSQLD_LAST_CMD --tc-heuristic-recover=ROLLBACK --innodb-read-only --log-error=$MYSQLTEST_VARDIR/tmp/log.err

# Rollback task will not be started at preshutdown if recovery mode is greater
# to 2.  Active transactions are not expected to rollback.
--error 1
--exec $MYSQLD_LAST_CMD --tc-heuristic-recover=ROLLBACK --innodb-force-recovery=3 --log-error=$MYSQLTEST_VARDIR/tmp/log.err

# Rollback task will be started at preshutdown of fast shutdown if force
# recovery is 2. But the transaction is deregistered instead of rollback.
--error 1
--exec $MYSQLD_LAST_CMD --tc-heuristic-recover=ROLLBACK --innodb-fast-shutdown=1 --innodb-force-recovery=2  --log-error=$MYSQLTEST_VARDIR/tmp/log.err

--let $restart_parameters= --innodb-read-only
--source include/start_mysqld.inc

# Verify that the transaction is still there.
SELECT count(*) FROM information_schema.innodb_trx;

--source include/kill_mysqld.inc

# Rollback task will be started at preshutdown of fast shutdown. The
# active transaction is rolled back.
--error 1
--exec $MYSQLD_LAST_CMD --tc-heuristic-recover=ROLLBACK --innodb-fast-shutdown=1 --log-error=$MYSQLTEST_VARDIR/tmp/log.err

--let $restart_parameters= --innodb-read-only
--source include/start_mysqld.inc
# Verify that the transaction is still there.
SELECT count(*) FROM information_schema.innodb_trx;

--remove_file $MYSQLTEST_VARDIR/tmp/log.err

--let $restart_parameters=
--source include/restart_mysqld.inc

# There should be no any transaction
--let $wait_condition= SELECT count(*) = 0 FROM information_schema.innodb_trx
--source include/wait_condition.inc

# Cleanup.
DROP TABLE t1;