Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Won't Fix
-
Affects Version/s: 5.5.37-galera
-
Fix Version/s: None
-
Component/s: None
-
Labels:
-
Environment:debian wheezy
3x master/master galera cluster
Description
Reproduction step:
my.cnf ... [server] wsrep_replicate_myisam=ON replicate_wild_ignore_table=a_local_database.% ... ...
node1> CREATE TABLE `a_local_database`.`a_table` ( `id` int NOT NULL AUTO_INCREMENT PRIMARY KEY, `data` varchar(64) NOT NULL ) ENGINE='MyISAM' COLLATE 'utf8_bin'; node2> CREATE TABLE `a_local_database`.`a_table` ( `id` int NOT NULL AUTO_INCREMENT PRIMARY KEY, `data` varchar(64) NOT NULL ) ENGINE='MyISAM' COLLATE 'utf8_bin'; Error in query (1050): Table 'a_table' already exists node1> INSERT INTO `a_local_database`.`a_table` VALUES(null,'node1'); 1 row inserted node2> SELECT * from `a_local_database`.`a_table`; +----+-------+ | id | data | +----+-------+ | 1 | node1 | +----+-------+ 1 row in set (0.00 sec)
======
As a general comment, precedence of replication filters should be explained in the documentation.
Gliffy Diagrams
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
I'm not sure these replication filters are expected to have any effect on Galera replication, but Nirbhay Choubey will be able to say for sure.
And indeed, if they don't work with Galera, it should be documented, I failed to find anything.