mirror of
https://github.com/MariaDB/server.git
synced 2025-11-28 17:36:30 +03:00
1ef50a34ec
* MDEV-16509 Improve wsrep commit performance with binlog disabled Release commit order critical section early after trx_commit_low() if binlog is not transaction coordinator. In order to avoid two phase commit, binlog_hton is not registered for THD during IO_CACHE population. Implemented a test which verifies that the transactions release commit order early. This optimization will change behavior during recovery as the commit is not two phase when binlog is off. Fixed and recorded wsrep-recover-v25 and wsrep-recover to match the behavior. * MDEV-18730 Ordering for wsrep binlog group commit Previously out of order execution was allowed for wsrep commits. Established proper ordering by populating wait_for_commit for every wsrep THD and making group commit leader to wait for prior commits before proceeding to trx_group_commit_leader(). * MDEV-18730 Added a test case to verify correct commit ordering * MDEV-16509, MDEV-18730 Review fixes Use WSREP_EMULATE_BINLOG() macro to decide if the binlog_hton should be registered. Whitespace/syntax fixes and cleanups. * MDEV-16509 Require binlog for galera_var_innodb_disallow_writes test If the commit to InnoDB is done in one phase, the native InnoDB behavior is that the transaction is committed in memory before it is persisted to disk. This means that the innodb_disallow_writes=ON may not prevent transaction to become visible to other readers before commit is completely over. On the other hand, if the commit is two phase (as it is with binlog), the transaction will be blocked in prepare phase. Fixed the test to use binlog, which enforces two phase commit, which in turn makes commit to block before the changes become visible to other connections. This guarantees that the test produces expected result.
115 lines
3.5 KiB
Plaintext
115 lines
3.5 KiB
Plaintext
#
|
|
# Verify that the wsrep XID gets updated in InnoDB rollback segment
|
|
# properly and can be recovered with --wsrep-recover
|
|
#
|
|
# The test runs the following scenarios:
|
|
#
|
|
# 1) The server is started but no SQL is run
|
|
# 2) DDL is executed
|
|
# 3) INSERT is executed
|
|
# 4) Two INSERTs are executed so that the first one in order will be
|
|
# blocked after certification and the second one before entering
|
|
# commit order critical section.
|
|
# 5) Two DMLs are executed so that the prepare step is run out of order.
|
|
# Both transactions are blocked before commit order critical section.
|
|
#
|
|
# After each scenario server is killed and the recovered position
|
|
# is validated.
|
|
#
|
|
|
|
--source include/have_wsrep.inc
|
|
--source include/have_innodb.inc
|
|
--source include/have_wsrep_provider.inc
|
|
--source include/have_debug_sync.inc
|
|
|
|
#
|
|
# Binlog option for recovery run. This must be set in the test because
|
|
# combinations file causes log-bin option to be set from command line,
|
|
# not via my.cnf.
|
|
#
|
|
--let $log_bin = `SELECT @@log_bin`
|
|
if ($log_bin) {
|
|
--let $wsrep_recover_binlog_opt = --log-bin
|
|
}
|
|
|
|
#
|
|
# Scenario 1
|
|
# The expected recovered seqno is 1 corresponding to initial cluster
|
|
# configuration change.
|
|
#
|
|
--source include/kill_mysqld.inc
|
|
--source wsrep-recover-step.inc
|
|
--echo Expect seqno 1
|
|
--echo $wsrep_recover_start_position_seqno
|
|
|
|
--let $restart_parameters = --wsrep-start-position=$wsrep_recover_start_position_uuid:$wsrep_recover_start_position_seqno
|
|
--source include/start_mysqld.inc
|
|
--source include/wait_wsrep_ready.inc
|
|
|
|
#
|
|
# Senario 2
|
|
# The expected recovered seqno is 3 corresponding to two configuration
|
|
# changes and CREATE TABLE
|
|
#
|
|
|
|
CREATE TABLE t1 (f1 INT PRIMARY KEY) ENGINE=InnoDB;
|
|
--source include/kill_mysqld.inc
|
|
--source wsrep-recover-step.inc
|
|
--echo Expect seqno 3
|
|
--echo $wsrep_recover_start_position_seqno
|
|
|
|
--let $restart_parameters = --wsrep-start-position=$wsrep_recover_start_position_uuid:$wsrep_recover_start_position_seqno
|
|
--source include/start_mysqld.inc
|
|
--source include/wait_wsrep_ready.inc
|
|
|
|
#
|
|
# Scenario 3
|
|
# The expected recovered seqno is 5 corresponding to three configuration
|
|
# changes, CREATE TABLE and INSERT.
|
|
#
|
|
# The expected wsrep_last_committed after the server is restarted is 6.
|
|
#
|
|
|
|
INSERT INTO t1 VALUES (5);
|
|
--source include/kill_mysqld.inc
|
|
--source wsrep-recover-step.inc
|
|
--echo Expect seqno 5
|
|
--echo $wsrep_recover_start_position_seqno
|
|
--let $restart_parameters = --wsrep-start-position=$wsrep_recover_start_position_uuid:$wsrep_recover_start_position_seqno
|
|
--source include/start_mysqld.inc
|
|
--source include/wait_wsrep_ready.inc
|
|
|
|
SELECT VARIABLE_VALUE `expect 6` FROM INFORMATION_SCHEMA.GLOBAL_STATUS WHERE VARIABLE_NAME = 'wsrep_last_committed';
|
|
|
|
#
|
|
# Scenario 4
|
|
#
|
|
# The INSERT gets prepared but not committed.
|
|
#
|
|
# This scenario is not applicable if binlog is not on since the
|
|
# commit is not 2PC.
|
|
#
|
|
# If binlog is on, the INSERT
|
|
# should be rolled back during recovery phase since it has not yet
|
|
# been logged into binlog.
|
|
#
|
|
if ($log_bin) {
|
|
--connect con1, localhost, root
|
|
SET DEBUG_SYNC = "ha_commit_trans_after_prepare SIGNAL after_prepare_reached WAIT_FOR continue";
|
|
--send INSERT INTO t1 VALUES (7)
|
|
|
|
--connection default
|
|
SET DEBUG_SYNC = "now WAIT_FOR after_prepare_reached";
|
|
--source include/kill_mysqld.inc
|
|
--source wsrep-recover-step.inc
|
|
--echo Expect seqno 6
|
|
--echo $wsrep_recover_start_position_seqno
|
|
--let $restart_parameters = --wsrep-start-position=$wsrep_recover_start_position_uuid:$wsrep_recover_start_position_seqno
|
|
--source include/start_mysqld.inc
|
|
--source include/wait_wsrep_ready.inc
|
|
--echo Expect 5
|
|
SELECT * FROM t1;
|
|
}
|
|
|
|
DROP TABLE t1;
|