MySQL Multi-Source Replication The  STOP REPLICA | SLAVE  statement can be used to stop a multi-source replica. By default, if you use the  STOP REPLICA | SLAVE  statement on a multi-source replica all channels are stopped. Optionally, use the  FOR CHANNEL  channel  clause to stop only a specific channel. mysql>  SHOW REPLICA STATUS FOR CHANNEL "source_1"\G mysql>  SHOW REPLICA STATUS FOR CHANNEL "source_2"\G 17.1.5.6 Stopping Multi-Source Replicas 17.1.5.7 Resetting Multi-Source Replicas mysql>  STOP SLAVE; Or from MySQL 8.0.22: mysql>  STOP REPLICA; mysql>  STOP SLAVE FOR CHANNEL "source_1"; Or from MySQL 8.0.22: mysql>  STOP REPLICA FOR CHANNEL "source_1"; mysql>  RESET SLAVE; Or from MySQL 8.0.22: mysql>  RESET REPLICA; mysql>  RESET SLAVE FOR CHANNEL "source_1"; Or from MySQL 8.0.22: mysql>  RESET REPLICA FOR CHANNEL "source_1"; •To stop all currently configured replication channels: •To stop only a named channel, use a  FOR CHANNEL  channel  clause: For the full syntax of the  STOP REPLICA | SLAVE  command and other available options, see Section 13.4.2.9, “STOP REPLICA | SLAVE Statement” . The  RESET REPLICA | SLAVE  statement can be used to reset a multi-source replica. By default, if you use the  RESET REPLICA | SLAVE  statement on a multi-source replica all channels are reset. Optionally, use the  FOR CHANNEL  channel  clause to reset only a specific channel. •To reset all currently configured replication channels: •To reset only a named channel, use a  FOR CHANNEL  channel  clause: For GTID-based replication, note that  RESET REPLICA | SLAVE  has no effect on the replica’s GTID execution history. If you want to clear this, issue  RESET MASTER  on the replica. RESET REPLICA | SLAVE  makes the replica forget its replication position, and clears the relay log, but it does not change any replication connection parameters (such as the source host name) or replication filters. If you want to remove these for a channel, issue  RESET REPLICA | SLAVE ALL . For the full syntax of the  RESET REPLICA | SLAVE  command and other available options, see Section 13.4.2.5, “RESET REPLICA | SLAVE Statement” . To monitor the status of replication channels the following options exist: •Using the replication Performance Schema tables. The first column of these tables is  Channel_Name . This enables you to write complex queries based on  Channel_Name  as a key. See Section 27.12.11, “Performance Schema Replication Tables” . 17.1.5.8 Monitoring Multi-Source Replication 3486