## 17.1.5.6 Stopping Multi-Source Replicas 

mysql> SHOW REPLICA STATUS FOR CHANNEL "source_1"\G mysql> SHOW REPLICA STATUS FOR CHANNEL "source_2"\G 

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. 

•To stop all currently configured replication channels: 

mysql> STOP SLAVE; Or from MySQL 8.0.22: mysql> STOP REPLICA; 

•To stop only a named channel, use a FOR CHANNEL channel  clause: 

mysql> STOP SLAVE FOR CHANNEL "source_1"; Or from MySQL 8.0.22: mysql> STOP REPLICA FOR CHANNEL "source_1"; 

For the full syntax of the STOP REPLICA | SLAVE  command and other available options, see Section 13.4.2.9, “STOP REPLICA | SLAVE Statement” . 

## 17.1.5.7 Resetting Multi-Source Replicas 

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: 

mysql> RESET SLAVE; Or from MySQL 8.0.22: mysql> RESET REPLICA; 

•To reset only a named channel, use a FOR CHANNEL channel  clause: 

mysql> RESET SLAVE FOR CHANNEL "source_1"; Or from MySQL 8.0.22: mysql> RESET REPLICA FOR CHANNEL "source_1"; 

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” . 

## 17.1.5.8 Monitoring Multi-Source Replication 

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” . 

