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
|
# ==== Purpose ====
#
# This script tests server behavior when a crash occurs during the
# execution of `XA COMMIT ... ONE PHASE`, just before the statement is
# committed in the internal transaction coordinator, when binary logging is
# disabled
#
# ==== Requirements ====
#
# Pre-conditions:
# PC1. Binary logging is disabled.
#
# After server restart:
# R1. There shouldn't be any changes to the data.
# R2. There shouldn't be any pending XA transactions visible with `XA
# RECOVER`.
#
# ==== Implementation ====
#
# 1. Setup scenario: create table and insert some records.
# 2. Start and execute an XA transaction containing an insert until before
# `XA COMMIT ... ONE PHASE`.
# 3. Crash the server during `XA COMMIT ... ONE PHASE` execution before
# commiting in the internal transaction coordinator.
# 4. Restart server and check:
# a. Error log for messages stating that SE recovery process rolled back
# a pending transaction.
# b. Error log for messages stating that XA recovery process didn't find
# any transaction needing recovery.
# c. There aren't any pending XA transaction listed in the output of `XA
# RECOVER`.
# d. There aren't changes to the table.
#
# ==== References ====
#
# WL#11300: Crash-safe XA + binary log
#
# Related tests:
# see extra/xa_crash_safe_tests/setup.inc
#
--source include/not_valgrind.inc
--source include/have_debug.inc
--source include/have_debug_sync.inc
--let $option_name = log_bin
--let $option_value = 0
--source include/only_with_option.inc
# 1. Setup scenario: create table and insert some records.
#
--let $xid_data = xid1
--let $xid = `SELECT CONCAT("X'", LOWER(HEX('$xid_data')), "',X'',1")`
--source extra/xa_crash_safe_tests/setup.inc
# 2. Start and execute an XA transaction containing an insert until before
# `XA COMMIT`.
#
--connect(con1, localhost, root,,)
--connection con1
--eval XA START $xid
INSERT INTO t1 VALUES (1);
--eval XA END $xid
# 3. Crash the server during `XA COMMIT` execution before commiting in the
# internal transaction coordinator.
#
--let $auxiliary_connection = default
--let $statement_connection = con1
--let $statement = XA COMMIT $xid ONE PHASE
--let $sync_point = before_commit_in_tc
--source include/execute_to_conditional_timestamp_sync_point.inc
--source include/kill_mysqld.inc
--source extra/xa_crash_safe_tests/cleanup_connection.inc
# 4. Restart server and check:
#
--source include/start_mysqld.inc
# 4.a. Error log for messages stating that SE recovery process rolled back
# a pending transaction.
#
--let $assert_select = Rolling back trx with id %, 1 rows to undo
--source extra/xa_crash_safe_tests/assert_se_recovery_message.inc
# 4.b. Error log for messages stating that XA recovery process didn't find
# any transaction needing recovery.
#
--let $assert_select = in InnoDB engine. No attempts to commit, rollback or prepare any transactions.
--source extra/xa_crash_safe_tests/assert_recovery_message.inc
# 4.c. There aren't any pending XA transaction listed in the output of `XA
# RECOVER`.
#
--let $expected_prepared_xa_count = 0
--source extra/xa_crash_safe_tests/assert_xa_recover.inc
# 4.d. There aren't changes to the table.
#
--let $expected_row_count = 1
--source extra/xa_crash_safe_tests/assert_row_count.inc
DROP TABLE t1;
|
