Debian Codegraph @

mysql-test/suite/rpl/t/rpl_skip_slave_err_warnings.test

raw
1 ###############################################################################
2 # Bug:#17581990:SLAVE SQL: COULD NOT EXECUTE QUERY EVENT. DETAILED ERROR: ;,
3 # ERROR_CODE: 0
4 #
5 # Problem:
6 # ========
7 # Setting replica-skip-errors=all on the slave will make mysql slave
8 # error log to grow continuously with the following warnings.
9 #
10 # [Warning] Slave SQL: Could not execute Query event.
11 # Detailed error: ;, Error_code: 0
12 #
13 # Test:
14 # =====
15 # Set up master slave replication. Set "replica-skip-errors=all" on the slve.
16 # Execute simple statments on master which does not cause any error on slave.
17 # Check that no warning should be generated on slave.
18 ###############################################################################
19 --source include/have_binlog_format_statement.inc
20 # Inorder to grep a specific error pattern in error log a fresh error log
21 # needs to be generated.
22 --source include/force_restart.inc
23 --source include/master-slave.inc
24
25 CREATE TABLE t1 (c1 INT) ENGINE=InnoDB;
26 INSERT INTO test.t1 VALUES (100);
27 DROP TABLE t1;
28 --source include/sync_slave_sql_with_master.inc
29
30 # Script produces different warning when executed along with MTS, hence added
31 # a generic replace regular expression.
32 --replace_regex /[0-9]{4}-[0-9]{2}-[0-9]{2} [0-9]{2}:[0-9]{2}:[0-9]{2} [0-9]+/--TIME--/ s/Worker .* end_log_pos [0-9]*; //
33 --let $grep_file=$MYSQLTEST_VARDIR/tmp/slave.err
34 --let $grep_pattern=Could not execute Query event.
35 --source include/grep_pattern.inc
36 --remove_file $grep_file
37
38 --source include/rpl_end.inc