mirror of
https://github.com/MariaDB/server.git
synced 2025-01-19 21:42:35 +01:00
eb75edfb2b
This makes it clear that the error code has nothing to do with errno. mysql-test/include/mtr_warnings.sql: Fixed suppression for new slave error messages mysql-test/lib/My/Test.pm: Use 'send' instead of 'print' to avoid errors about "wrong class ... back attempt" mysql-test/lib/v1/mtr_report.pl: Fixed suppression for new slave error messages mysql-test/mysql-test-run.pl: Fixed suppression for new slave error messages Removed warning from perl 5.16.2 about arrays mysql-test/r/flush_read_lock.result: Fixed suppression for new slave error messages sql/rpl_reporting.cc: Instead of writing "Errcode" to the log for Slave errors, use "Internal MariaDB error code"
172 lines
4.3 KiB
Text
172 lines
4.3 KiB
Text
# ==== Purpose ====
|
|
#
|
|
# Verify that --slave-skip-errors works correctly. The error messages
|
|
# specified by --slave-skip-errors on slave should be ignored. If
|
|
# such errors occur, they should not be reported and not cause the
|
|
# slave to stop.
|
|
#
|
|
# ==== Method ====
|
|
#
|
|
# We run the slave with --slave-skip-errors=1062 (the code for
|
|
# duplicate key). Then we have two set of tests. In the first
|
|
# set, we insert value 1 in a table on the slave, and then, on
|
|
# master, we insert value 1 in the table. In the second set, we
|
|
# insert several values on the master, disable the binlog and
|
|
# delete one of the values and re-enable the binlog. Right after,
|
|
# we perform an update on the set of values in order to generate
|
|
# a duplicate key on the slave. The errors should be ignored on
|
|
# the slave.
|
|
#
|
|
# ==== Related bugs ====
|
|
#
|
|
# BUG#28839: Errors in strict mode silently stop SQL thread if --slave-skip-errors exists
|
|
# bug in this test: BUG#30594: rpl.rpl_skip_error is nondeterministic:
|
|
# BUG#39393: slave-skip-errors does not work when using ROW based replication
|
|
|
|
source include/master-slave.inc;
|
|
source include/have_innodb.inc;
|
|
|
|
--echo ==== Test Without sql_mode=strict_trans_tables ====
|
|
|
|
--echo [on master]
|
|
create table t1 (n int not null primary key);
|
|
|
|
--echo [on slave]
|
|
sync_slave_with_master;
|
|
insert into t1 values (1);
|
|
|
|
--echo [on master]
|
|
connection master;
|
|
# Here we expect (ignored) error, since 1 is already in slave table
|
|
insert into t1 values (1);
|
|
# These should work fine
|
|
insert into t1 values (2),(3);
|
|
|
|
sync_slave_with_master;
|
|
--echo [on slave]
|
|
select * from t1 order by n;
|
|
|
|
--echo ==== Test With sql_mode=strict_trans_tables ====
|
|
insert into t1 values (7),(8);
|
|
--echo [on master]
|
|
connection master;
|
|
set sql_mode=strict_trans_tables;
|
|
insert into t1 values (7), (8), (9);
|
|
--echo [on slave]
|
|
sync_slave_with_master;
|
|
select * from t1 order by n;
|
|
source include/check_slave_is_running.inc;
|
|
|
|
--echo ==== Clean Up ====
|
|
connection master;
|
|
drop table t1;
|
|
sync_slave_with_master;
|
|
# End of 4.1 tests
|
|
|
|
#
|
|
# #28839 Errors in strict mode silently stop SQL thread if --slave-skip-errors exists
|
|
#
|
|
connection master;
|
|
create table t1(a int primary key);
|
|
insert into t1 values (1),(2);
|
|
SET SQL_LOG_BIN=0;
|
|
delete from t1;
|
|
SET SQL_LOG_BIN=1;
|
|
set sql_mode=strict_trans_tables;
|
|
insert into t1 values (1), (2), (3);
|
|
|
|
--echo [on slave]
|
|
sync_slave_with_master;
|
|
select * from t1;
|
|
source include/check_slave_is_running.inc;
|
|
|
|
|
|
--echo ==== Clean Up ====
|
|
|
|
connection master;
|
|
drop table t1;
|
|
sync_slave_with_master;
|
|
# End of 5.0 tests
|
|
|
|
#
|
|
# BUG#39393: slave-skip-errors does not work when using ROW based replication
|
|
#
|
|
--echo ==== Using Innodb ====
|
|
|
|
connection master;
|
|
|
|
SET SQL_LOG_BIN=0;
|
|
CREATE TABLE t1(id INT NOT NULL PRIMARY KEY, data INT) Engine=InnoDB;
|
|
SHOW CREATE TABLE t1;
|
|
SET SQL_LOG_BIN=1;
|
|
|
|
connection slave;
|
|
|
|
call mtr.add_suppression("Slave SQL.*Could not execute .*te_rows event on table test.t.; Duplicate entry.* error.* 1062");
|
|
|
|
CREATE TABLE t1(id INT NOT NULL PRIMARY KEY, data INT) Engine=InnoDB;
|
|
SHOW CREATE TABLE t1;
|
|
|
|
connection master;
|
|
|
|
INSERT INTO t1 VALUES(1, 1);
|
|
INSERT INTO t1 VALUES(2, 1);
|
|
INSERT INTO t1 VALUES(3, 1);
|
|
INSERT INTO t1 VALUES(4, 1);
|
|
|
|
SET SQL_LOG_BIN=0;
|
|
DELETE FROM t1 WHERE id = 4;
|
|
SET SQL_LOG_BIN=1;
|
|
UPDATE t1 SET id= id + 3, data = 2;
|
|
|
|
sync_slave_with_master;
|
|
|
|
let $error= query_get_value("SHOW SLAVE STATUS", Last_SQL_Error, 1);
|
|
echo $error;
|
|
|
|
--echo **** We cannot execute a select as there are differences in the
|
|
--echo **** behavior between STMT and RBR.
|
|
|
|
--echo ==== Using MyIsam ====
|
|
|
|
connection master;
|
|
|
|
SET SQL_LOG_BIN=0;
|
|
CREATE TABLE t2(id INT NOT NULL PRIMARY KEY, data INT) Engine=MyIsam;
|
|
SHOW CREATE TABLE t2;
|
|
SET SQL_LOG_BIN=1;
|
|
|
|
connection slave;
|
|
|
|
CREATE TABLE t2(id INT NOT NULL PRIMARY KEY, data INT) Engine=MyIsam;
|
|
SHOW CREATE TABLE t2;
|
|
|
|
connection master;
|
|
|
|
INSERT INTO t2 VALUES(1, 1);
|
|
INSERT INTO t2 VALUES(2, 1);
|
|
INSERT INTO t2 VALUES(3, 1);
|
|
INSERT INTO t2 VALUES(5, 1);
|
|
|
|
SET SQL_LOG_BIN=0;
|
|
DELETE FROM t2 WHERE id = 5;
|
|
SET SQL_LOG_BIN=1;
|
|
UPDATE t2 SET id= id + 3, data = 2;
|
|
|
|
sync_slave_with_master;
|
|
|
|
let $error= query_get_value("SHOW SLAVE STATUS", Last_SQL_Error, 1);
|
|
echo $error;
|
|
|
|
--echo **** We cannot execute a select as there are differences in the
|
|
--echo **** behavior between STMT and RBR.
|
|
|
|
--echo ==== Clean Up ====
|
|
|
|
connection master;
|
|
|
|
DROP TABLE t1;
|
|
DROP TABLE t2;
|
|
|
|
sync_slave_with_master;
|
|
--source include/rpl_end.inc
|