slave-skip-errors ignored in RBR mode.
Bug #903798 reported by
Alexey Zilber
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MariaDB |
Won't Fix
|
Low
|
Kristian Nielsen |
Bug Description
This looks like a bug that was fixed in Mysql 5.1.35. I just hit it in MariaDB 5.2.10.
I'm experiencing identical behavior to the bug filed here: http://
To replicate the error, I have 1 master, and 1 slave.
All servers have binlog_format = MIXED and slave-skip-
On slave 1, drop a database. Slave 1 will report:
Last_SQL_Errno: 1146
-Alex
tags: | added: replication upstream |
Changed in maria: | |
assignee: | Michael Widenius (monty) → Kristian Nielsen (knielsen) |
importance: | Undecided → Medium |
To post a comment you must log in.
Error 'Table .. does not exist' suggests that you are trying a slightly different scenario comparing to the one you described in the original bug. There was no CREATE TABLE hidden from slave, only DML (DELETE).
I am trying the scenario that you and Sveta described in the MySQL bug, and it works all right for me, both on MariaDB 5.2.10 and MySQL 5.1.60. However, a slightly different one, which involves DDL, fails, also both on MariaDB and MySQL, with the exact error that you mentioned. Something like this:
SET binlog_ format= 'row';
SET SQL_LOG_BIN=0;
CREATE TABLE t ( i INT );
INSERT INTO t VALUES (1);
SET SQL_LOG_BIN=1;
DELETE FROM t;
# check slave status, observe error 1146 and slave SQL thread not running.
Could you please confirm that's what you encountered?
I suppose this flow has never been fixed, or possibly was broken again. I It fails on MySQL 5.1.60 and 5.1.57, but I don't have older versions to check.