Allow Galera to ignore MySQL's replication filters

Bug #1371565 reported by Przemek
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
MySQL patches by Codership
Status tracked in 5.6
5.5
New
Undecided
Unassigned
5.6
New
Undecided
Unassigned
Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC
Status tracked in 5.6
5.5
Won't Fix
Wishlist
Unassigned
5.6
Confirmed
Wishlist
Unassigned

Bug Description

It seems that all the replication filters available in standard MySQL async replication also apply to Galera replication.
This is sometimes a problematic situation if one wants to mix Galera and async replication topologies. For example, setting a slave filter on Galera node acting as an async slave makes this node inconsistent with others if you do a direct write to filtered tables on this node - no galera peers will receive these updates. This and many other scenarios makes the situation within the cluster very complicated in case you need to change async replication topology or when SST happens between the nodes with different filters applied.
Sometimes you may need to apply some replication filtering for async replication but in the same time it is highly desired to have consistent data within Galera based cluster. Let's say you need two independent Galera clusters where only some data should be replicated between them in async way - right now it seems to be impossible without making the clusters inconsistent internally.

I would like to see an option to ignore all the MySQL filters in Galera replication while still let them affect the asynchronous replication.

Przemek (pmalkowski)
description: updated
Revision history for this message
Przemek (pmalkowski) wrote :
Revision history for this message
Nilnandan Joshi (nilnandan-joshi) wrote :

This is actually a feature request or improvement request. mysql filters affecting galera is a fact so having a variable to disable filters for galera would be useful. Setting it to confirmed.

Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-1180

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.