mirror of
https://github.com/MariaDB/server.git
synced 2025-08-27 13:04:36 +03:00
09c80e12c5
Major replication test framework cleanup. This does the following:
- Ensure that all tests clean up the replication state when they
finish, by making check-testcase check the output of SHOW SLAVE STATUS.
This implies:
- Slave must not be running after test finished. This is good
because it removes the risk for sporadic errors in subsequent
tests when a test forgets to sync correctly.
- Slave SQL and IO errors must be cleared when test ends. This is
good because we will notice if a test gets an unexpected error in
the slave threads near the end.
- We no longer have to clean up before a test starts.
- Ensure that all tests that wait for an error in one of the slave
threads waits for a specific error. It is no longer possible to
source wait_for_slave_[sql|io]_to_stop.inc when there is an error
in one of the slave threads. This is good because:
- If a test expects an error but there is a bug that causes
another error to happen, or if it stops the slave thread without
an error, then we will notice.
- When developing tests, wait_for_*_to_[start|stop].inc will fail
immediately if there is an error in the relevant slave thread.
Before this patch, we had to wait for the timeout.
- Remove duplicated and repeated code for setting up unusual replication
topologies. Now, there is a single file that is capable of setting
up arbitrary topologies (include/rpl_init.inc, but
include/master-slave.inc is still available for the most common
topology). Tests can now end with include/rpl_end.inc, which will clean
up correctly no matter what topology is used. The topology can be
changed with include/rpl_change_topology.inc.
- Improved debug information when tests fail. This includes:
- debug info is printed on all servers configured by include/rpl_init.inc
- User can set $rpl_debug=1, which makes auxiliary replication files
print relevant debug info.
- Improved documentation for all auxiliary replication files. Now they
describe purpose, usage, parameters, and side effects.
- Many small code cleanups:
- Made have_innodb.inc output a sensible error message.
- Moved contents of rpl000017-slave.sh into rpl000017.test
- Added mysqltest variables that expose the current state of
disable_warnings/enable_warnings and friends.
- Too many to list here: see per-file comments for details.
48 lines
1.4 KiB
Plaintext
48 lines
1.4 KiB
Plaintext
source include/master-slave.inc;
|
|
|
|
CALL mtr.add_suppression("Statement may not be safe to log in statement format.");
|
|
|
|
create table t1(n int);
|
|
# Use of get_lock gives a warning for unsafeness if binlog_format=statement
|
|
--disable_warnings
|
|
insert into t1 values(get_lock("lock",2));
|
|
--enable_warnings
|
|
dirty_close master;
|
|
connection master1;
|
|
select get_lock("lock",2);
|
|
|
|
select release_lock("lock");
|
|
#ignore
|
|
disable_query_log;
|
|
let $1=2000;
|
|
while ($1)
|
|
{
|
|
do get_lock("lock",2);
|
|
do release_lock("lock");
|
|
dec $1;
|
|
}
|
|
enable_query_log;
|
|
sync_slave_with_master;
|
|
select get_lock("lock",3);
|
|
select * from t1;
|
|
# There is no point in testing REPLICATIION of the IS_*_LOCK
|
|
# functions; slave does not run with the same concurrency context as
|
|
# master (generally in slave we can't know that on master this lock
|
|
# was already held by another connection and so that the the
|
|
# get_lock() we're replicating timed out on master hence returned 0,
|
|
# or that the is_free_lock() we're playing returned 0 etc.
|
|
# But here all we do is test these functions outside of replication.
|
|
select is_free_lock("lock"), is_used_lock("lock") = connection_id();
|
|
explain extended select is_free_lock("lock"), is_used_lock("lock");
|
|
# Check lock functions
|
|
select is_free_lock("lock2");
|
|
select is_free_lock(NULL);
|
|
connection master1;
|
|
drop table t1;
|
|
sync_slave_with_master;
|
|
|
|
|
|
--source include/rpl_end.inc
|
|
|
|
# End of 4.1 tests
|