Replication and Binary Logging Options and Variables Section 17.2.5, “How Servers Evaluate Replication Filtering Rules” . You can also create such a filter by issuing a  CHANGE REPLICATION FILTER REPLICATE_DO_TABLE  statement. This option supports channel specific replication filters, enabling multi-source replicas to use specific filters for different sources. To configure a channel specific replication filter on a channel named channel_1  use  --replicate-do-table: channel_1 : db_name.tbl_name . In this case, the first colon is interpreted as a separator and subsequent colons are literal colons. See Section 17.2.5.4, “Replication Channel Based Filters”  for more information. Note Global replication filters cannot be used on a MySQL server instance that is configured for Group Replication, because filtering transactions on some servers would make the group unable to reach agreement on a consistent state. Channel specific replication filters can be used on replication channels that are not directly involved with Group Replication, such as where a group member also acts as a replica to a source that is outside the group. They cannot be used on the  group_replication_applier  or  group_replication_recovery channels. This option affects only statements that apply to tables. It does not affect statements that apply only to other database objects, such as stored routines. To filter statements operating on stored routines, use one or more of the  --replicate-*-db  options. Creates a replication filter by telling the replication SQL thread not to replicate any statement that updates the specified table, even if any other tables might be updated by the same statement. To specify more than one table to ignore, use this option multiple times, once for each table. This works for cross-database updates, in contrast to  --replicate-ignore-db . See Section 17.2.5, “How Servers Evaluate Replication Filtering Rules” . You can also create such a filter by issuing a  CHANGE REPLICATION FILTER REPLICATE_IGNORE_TABLE  statement. This option supports channel specific replication filters, enabling multi-source replicas to use specific filters for different sources. To configure a channel specific replication filter on a channel named channel_1  use  --replicate-ignore-table: channel_1 : db_name.tbl_name . In this case, the first colon is interpreted as a separator and subsequent colons are literal colons. See Section 17.2.5.4, “Replication Channel Based Filters”  for more information. Global replication filters cannot be used on a MySQL server instance that is configured for Group Replication, because filtering transactions on some servers would make the group unable to reach agreement on a consistent state. Channel specific replication filters can be used on replication channels that are not directly involved with Group Replication, such as where a group member also acts as a replica to a source that is outside the group. They cannot be used on Note 3511 Command-Line Format --replicate-ignore-table=name Type String • --replicate-ignore-table= db_name.tbl_name