Replication and Binary Logging Options and Variables as literal colons. For example, to configure a channel specific replication filter on a channel named channel_1 , use: If you use a colon but do not specify a channel name, the option configures the replication filter for the default replication channel. 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 the  group_replication_applier  or  group_replication_recovery channels. This option is for use on replicas. The default is 0 ( FALSE ). With this option set to 1 ( TRUE ), the replica does not skip events that have its own server ID. This setting is normally useful only in rare configurations. When binary logging is enabled on a replica, the combination of the  --replicate-same-server-id and  --log-slave-updates  options on the replica can cause infinite loops in replication if the server is part of a circular replication topology. (In MySQL 8.0, binary logging is enabled by default, and replica update logging is the default when binary logging is enabled.) However, the use of global transaction identifiers (GTIDs) prevents this situation by skipping the execution of transactions that have already been applied. If  gtid_mode=ON  is set on the replica, you can start the server with this combination of options, but you cannot change to any other GTID mode while the server is running. If any other GTID mode is set, the server does not start with this combination of options. By default, the replication I/O thread does not write binary log events to the relay log if they have the replica’s server ID (this optimization helps save disk usage). If you want to use  --replicate-same- server-id , be sure to start the replica with this option before you make the replica read its own events that you want the replication SQL thread to execute. Creates a replication filter by telling the replication SQL thread to restrict replication to statements where any of the updated tables match the specified database and table name patterns. Patterns can contain the  %  and  _  wildcard characters, which have the same meaning as for the  LIKE  pattern- matching operator. To specify more than one table, use this option multiple times, once for each table. This works for cross-database updates. See Section 17.2.5, “How Servers Evaluate Replication 3513 • --replicate-wild-do-table= db_name.tbl_name Command-Line Format --replicate-wild-do-table=name Type String Command-Line Format --replicate-same-server-id[={OFF|ON}] Type Boolean Default Value OFF • --replicate-same-server-id Note shell>  mysqld --replicate-rewrite-db= channel_1 : db_name1 -> db_name2