mirror of
https://github.com/MariaDB/server.git
synced 2025-01-22 06:44:16 +01:00
3889dffcc0
Problem 1: The test waits for an error in the slave sql thread,
then resolves the error and issues 'start slave'. However, there
is a gap between when the error is reported and the slave sql
thread stops. If this gap was long, the slave would still be
running when 'start slave' happened, so 'start slave' would fail
and cause a test failure.
Fix 1: Made wait_for_slave_sql_error wait for the slave to stop
instead of wait for error in the IO thread. After stopping, the
error code is verified. If the error code is wrong, debug info
is printed. To print debug info, the debug printing code in
wait_for_slave_param.inc was moved out to a new file,
show_rpl_debug_info.inc.
Problem 2: rpl_stm_mystery22 is a horrible name, the comments in
the file didn't explain anything useful, the test was generally
hard to follow, and the test was essentially duplicated between
rpl_stm_mystery22 and rpl_row_mystery22.
Fix 2: The test is about conflicts in the slave SQL thread,
hence I renamed the tests to rpl_{stm,row}_conflicts. Refactored
the test so that the work is done in
extra/rpl_tests/rpl_conflicts.inc, and
rpl.rpl_{row,stm}_conflicts merely sets some variables and then
sourced extra/rpl_tests/rpl_conflicts.inc.
The tests have been rewritten and comments added.
Problem 3: When calling wait_for_slave_sql_error.inc, you always
want to verify that the sql thread stops because of the expected
error and not because of some other error. Currently,
wait_for_slave_sql_error.inc allows the caller to omit the error
code, in which case all error codes are accepted.
Fix 3: Made wait_for_slave_sql_error.inc fail if no error code
is given. Updated rpl_filter_tables_not_exist accordingly.
Problem 4: rpl_filter_tables_not_exist had a typo, the dollar
sign was missing in a 'let' statement.
Fix 4: Added dollar sign.
Problem 5: When replicating from other servers than the one named
'master', the wait_for_slave_* macros were unable to print debug
info on the master.
Fix 5: Replace parameter $slave_keep_connection by
$master_connection.
54 lines
1.4 KiB
Text
54 lines
1.4 KiB
Text
stop slave;
|
|
drop table if exists t1,t2,t3,t4,t5,t6,t7,t8,t9;
|
|
reset master;
|
|
reset slave;
|
|
drop table if exists t1,t2,t3,t4,t5,t6,t7,t8,t9;
|
|
start slave;
|
|
==== Initialize ====
|
|
[on master]
|
|
CREATE TABLE t1(a INT PRIMARY KEY);
|
|
[on slave]
|
|
==== Test: SQL thread sees 'INSERT' of existing key ====
|
|
---- Prepare slave so that it will get duplicate key error ----
|
|
INSERT INTO t1 VALUES (1);
|
|
---- Insert rows on master ----
|
|
[on master]
|
|
INSERT INTO t1 VALUES (1);
|
|
SELECT * FROM t1;
|
|
a
|
|
1
|
|
[on slave]
|
|
---- Wait until slave stops with an error ----
|
|
Last_SQL_Error = Error 'Duplicate entry '1' for key 'PRIMARY'' on query. Default database: 'test'. Query: 'INSERT INTO t1 VALUES (1)' (expected "duplicate key" error)
|
|
SELECT * FROM t1;
|
|
a
|
|
1
|
|
---- Resolve the conflict on the slave and restart SQL thread ----
|
|
DELETE FROM t1 WHERE a = 1;
|
|
START SLAVE SQL_THREAD;
|
|
---- Sync slave and verify that there is no error ----
|
|
Last_SQL_Error = '' (expected no error)
|
|
SELECT * FROM t1;
|
|
a
|
|
1
|
|
==== Test: SQL thread sees 'DELETE' of non-existing row ====
|
|
---- On master, insert two rows, the second with binlogging off ----
|
|
[on master]
|
|
DELETE FROM t1;
|
|
INSERT INTO t1 VALUES (1);
|
|
[on slave]
|
|
DELETE FROM t1 WHERE a = 1;
|
|
---- On master, remove the row that does not exist on slave ----
|
|
[on master]
|
|
DELETE FROM t1 WHERE a = 1;
|
|
SELECT * FROM t1;
|
|
a
|
|
[on slave]
|
|
---- Sync slave and verify that there is no error ----
|
|
Last_SQL_Error = (expected no error)
|
|
SELECT * FROM t1;
|
|
a
|
|
==== Clean up ====
|
|
[on master]
|
|
DROP TABLE t1;
|
|
[on slave]
|