[MDEV-6229] galera replication filter & myisam does not filter Created: 2014-05-11 Updated: 2018-07-27 Resolved: 2014-06-20 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | None |
| Affects Version/s: | 5.5.37-galera |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | doekia | Assignee: | Nirbhay Choubey (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | galera, replication | ||
| Environment: |
debian wheezy |
||
| Issue Links: |
|
||||
| Description |
|
Reproduction step:
====== |
| Comments |
| Comment by Elena Stepanova [ 2014-05-11 ] |
|
I'm not sure these replication filters are expected to have any effect on Galera replication, but nirbhay_c will be able to say for sure. |
| Comment by doekia [ 2014-06-18 ] |
|
Any feedback regarding such? |
| Comment by Nirbhay Choubey (Inactive) [ 2014-06-18 ] |
|
"replicate_wild_ignore_table" affects replication slave thread which is not used in Galera replication. |
| Comment by Nirbhay Choubey (Inactive) [ 2014-06-20 ] |
|
Hi doekia, I looked futher into the replication filter support and it turned out that Added a note in the Galera limitations page : |
| Comment by Nirbhay Choubey (Inactive) [ 2014-06-20 ] |
|
Its a limitation for MyISAM engine. Closing it as won't fix as replication of MyISAM tables is still considered 'experimental' in Galera. |