mirror/mariadb
1
0
Fork 0
mirror of https://github.com/MariaDB/server.git synced 2025-01-20 05:52:27 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions
mariadb/mysql-test/suite/rpl/t/rpl_mdev359.test

33 lines
1.1 KiB
Text
Raw Normal View History

MDEV-4254 Semisync plugins to link statically into MariaDB fix semisync plugins and tests to work with both with static and dynamic linking
2013-04-09 23:28:21 +02:00
--source include/have_semisync.inc
MDEV-359: Server crash when SET GLOBAL rpl_semi_sync_master_enabled = OFF The semisync code does a fast-but-unsafe check for enabled or not without lock, followed by a slow-but-safe check under lock. However, if the slow check failed, the code still referenced not valid data (in an assert() expression), causing a crash. Fixed by not running the incorrect assert when semisync is disabled.
2012-06-21 11:52:54 +02:00
--source include/not_embedded.inc
--source include/have_debug_sync.inc
MDEV-359: Fix another case where switch-off semisync could cause a race that ended with server crash. This one was when the code releases and reaquires the lock with pthread_cond_wait() - and semisync is switched off meanwhile.
2012-06-21 19:02:53 +02:00
--source include/have_binlog_format_mixed_or_statement.inc
fixing the order of includes in the rpl_mdev359.test
2012-06-21 14:00:19 +02:00
--source include/master-slave.inc
MDEV-359: Server crash when SET GLOBAL rpl_semi_sync_master_enabled = OFF The semisync code does a fast-but-unsafe check for enabled or not without lock, followed by a slow-but-safe check under lock. However, if the slow check failed, the code still referenced not valid data (in an assert() expression), causing a crash. Fixed by not running the incorrect assert when semisync is disabled.
2012-06-21 11:52:54 +02:00
# MDEV-359: There was a server crash when the code first checks if semisync
# is enabled without lock, then if so takes the lock and tests again.
# If semisync was disabled in-between the first and the second test, an
# assert was incorrectly made that referenced a NULL pointer.
#
# This tests uses debug_sync to pause one thread at the critical point in
# the code, disable the semisync, and then continue the paused thread.
CREATE TABLE t1 (a INT) ENGINE=MyISAM;
SET GLOBAL rpl_semi_sync_master_enabled = ON;
--connection master1
SET DEBUG_SYNC = "rpl_semisync_master_commit_trx_before_lock SIGNAL m1_ready WAIT_FOR m1_cont";
--send
INSERT INTO t1 SELECT * FROM t1;
--connection master
SET DEBUG_SYNC= "now WAIT_FOR m1_ready";
SET GLOBAL rpl_semi_sync_master_enabled = OFF;
SET DEBUG_SYNC= "now SIGNAL m1_cont";
--connection master1
--reap
connection master;
DROP TABLE t1;
mtr: check that tests clean up debug_sync. fix tests that didn't.
2014-01-27 12:10:53 +01:00
SET DEBUG_SYNC= "RESET";
MDEV-359: Server crash when SET GLOBAL rpl_semi_sync_master_enabled = OFF The semisync code does a fast-but-unsafe check for enabled or not without lock, followed by a slow-but-safe check under lock. However, if the slow check failed, the code still referenced not valid data (in an assert() expression), causing a crash. Fixed by not running the incorrect assert when semisync is disabled.
2012-06-21 11:52:54 +02:00
--source include/rpl_end.inc
Reference in a new issue Copy permalink