# Filter out certain meta-data DML from MySQL replication

**URL:** <https://forums.percona.com/t/filter-out-certain-meta-data-dml-from-mysql-replication/11263>\
**Category:** Percona XtraDB Cluster 5.x\
**Created:** [July 8, 2021, 5:19pm UTC](https://forums.percona.com/t/filter-out-certain-meta-data-dml-from-mysql-replication/11263 "2021-07-08T17:19:26Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![rahulsri\_percona](https://avatars.discourse-cdn.com/v4/letter/r/f19dbf/32.png) [@rahulsri\_percona](https://forums.percona.com/u/rahulsri_percona)\
**Post date:** [July 8, 2021, 5:19pm UTC](https://forums.percona.com/t/filter-out-certain-meta-data-dml-from-mysql-replication/11263/1 "2021-07-08T17:19:26Z")

</div>

I am using PXC 5.7.x MySQL multi-master cluster which is also configured to be master slave with other clusters across geographical regions. I am using RSU. For DB change automation and tracking I am testing liquibase S/W automation which creates its own meta-data tables on each node for tracking purpose. Is there a way for me to not replicate any meta-data inserted (DML operations) on those tables created by liquibase to any other nodes which are part of multi-master replication or master slave replication setup i.e. filter them. But I want rest of the data to be replicated as usual. And how I can achieve this?

---

<div class="post-metadata">

**Author:** ![matthewb](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/matthewb/32/34_2.png) [@matthewb](https://forums.percona.com/u/matthewb)\
**Post date:** [July 8, 2021, 6:31pm UTC](https://forums.percona.com/t/filter-out-certain-meta-data-dml-from-mysql-replication/11263/2 "2021-07-08T18:31:20Z")

</div>

Hello @rahulsri_percona,  
For asynchronous replication you can use the normal [replication filters.](https://dev.mysql.com/doc/refman/8.0/en/change-replication-filter.html) Just put that meta db to ignore and you’re set.

---

<div class="post-metadata">

**Author:** ![rahulsri\_percona](https://avatars.discourse-cdn.com/v4/letter/r/f19dbf/32.png) [@rahulsri\_percona](https://forums.percona.com/u/rahulsri_percona)\
**Post date:** [July 8, 2021, 7:25pm UTC](https://forums.percona.com/t/filter-out-certain-meta-data-dml-from-mysql-replication/11263/3 "2021-07-08T19:25:33Z")

</div>

Thanks. We are using Multi-master Galera replication within a cluster. So it is synchronous replication in other words, when a transaction commits, all nodes have the same value. What option is available in this particular situation?

---

<div class="post-metadata">

**Author:** ![matthewb](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/matthewb/32/34_2.png) [@matthewb](https://forums.percona.com/u/matthewb)\
**Post date:** [July 8, 2021, 10:22pm UTC](https://forums.percona.com/t/filter-out-certain-meta-data-dml-from-mysql-replication/11263/4 "2021-07-08T22:22:50Z")

</div>

> [@rahulsri\_percona](#):
>
> Multi-master Galera replication

That is an invalid statement; that’s why I assumed you were talking about async replication. Galera can only be multi-master, there is no other option, so saying “multi-master galera replication” doesn’t make sense.

There is no built-in way to filter galera replication. That defeats the entire purpose behind galera replication. The purpose is that every node always has the same data. Any violation of this is a cluster-wide violation.

---

<div class="post-metadata">

**Author:** ![rahulsri\_percona](https://avatars.discourse-cdn.com/v4/letter/r/f19dbf/32.png) [@rahulsri\_percona](https://forums.percona.com/u/rahulsri_percona)\
**Post date:** [July 8, 2021, 10:38pm UTC](https://forums.percona.com/t/filter-out-certain-meta-data-dml-from-mysql-replication/11263/5 "2021-07-08T22:38:31Z")

</div>

I got it that --\>There is no built-in way to filter galera replication. Thanks