# Master-master asyn replication between two PXC clusters and replicate-ignore-table

**URL:** <https://forums.percona.com/t/master-master-asyn-replication-between-two-pxc-clusters-and-replicate-ignore-table/4315>\
**Category:** Percona XtraDB Cluster 5.x\
**Created:** [July 22, 2015, 3:09pm UTC](https://forums.percona.com/t/master-master-asyn-replication-between-two-pxc-clusters-and-replicate-ignore-table/4315 "2015-07-22T15:09:28Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![pxc127](https://avatars.discourse-cdn.com/v4/letter/p/b782af/32.png) [@pxc127](https://forums.percona.com/u/pxc127)\
**Post date:** [July 22, 2015, 3:09pm UTC](https://forums.percona.com/t/master-master-asyn-replication-between-two-pxc-clusters-and-replicate-ignore-table/4315/1 "2015-07-22T15:09:28Z")

</div>

Hello,

We have set up master-master async replication between two 3 node 5.6.24 PXC clusters.  
One table contains environment specific data and we need to exclude this table from the bi-directional replication.  
However, if we set replicate-ignore-table on the async slave node, the table is out of sync between the nodes in the same cluster.

It seems replicate-ignore-table affects async Mysql replication between the clusters and Galera replication within the cluster.

Is there any way we can work around this problem?

Thanks.

---

<div class="post-metadata">

**Author:** ![jrivera](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/jrivera/32/13_2.png) [@jrivera](https://forums.percona.com/u/jrivera)\
**Post date:** [July 27, 2015, 6:46pm UTC](https://forums.percona.com/t/master-master-asyn-replication-between-two-pxc-clusters-and-replicate-ignore-table/4315/2 "2015-07-27T18:46:30Z")

</div>

An existing bug/feature request confirms this behavior and there is no fix nor workaround AFAIK.

[url][https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1371565[/url]](https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1371565%5B/url%5D)

I hope this helps.