Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Won't Fix
-
5.5.33a-galera
Description
If a server is started with binlog-ignore-db or binlog-do-db, Galera still magically replicates DDL statements which relate to the databases chosen to be ignored (even although the statements are not written to the binary log).
DML works as expected.
The problem is not limited to breaking rather confusing rules for SBR vs RBR, but shows up in the simplest possible case:
- start 1st node with --binlog-ignore-db=test;
|
- start 2nd node with --binlog-ignore-db=test;
|
- synchronize the nodes;
|
- connect to the 1st node, set test as a default schema (if it's MySQL client, run USE test);
|
- run CREATE TABLE t (i INT PRIMARY KEY);
|
- connect to the 2nd node, set test as a default schema;
|
- run SHOW TABLES to see that the table is there; <<<=== This is the wrong behavior
|
- run INSERT INTO t VALUES (1);
|
- check that the table is still empty on the 1st node.
|
- optionally: run SHOW BINLOG EVENTS on the 1st node to see that CREATE TABLE statement is not there.
|
bzr version-info
revision-id: seppo.jaakola@codership.com-20120612212332-h2ay711nh1vhaiob
|
date: 2012-06-13 00:23:32 +0300
|
build-date: 2012-08-01 04:51:46 +0400
|
revno: 3341
|
Note: If it's another limitation, it should be added to http://www.codership.com/wiki/doku.php?id=limitations