content_image/850231.jpg content_image/850232.jpg
<img src='content_image/850231.jpg'>

Because it is the replica that drives the replication process, very little information is available in this report. 

For replicas that were started with the --report-host  option and are connected to the source, the SHOW REPLICAS | SHOW SLAVE HOSTS  statement on the source shows basic information about the replicas. The output includes the ID of the replica server, the value of the --report-host  option, the connecting port, and source ID: 

## 17.1.7.2 Pausing Replication on the Replica 

mysql> SHOW REPLICAS; 

<img src='content_image/850232.jpg'>

1 row in set (0.00 sec) 

You can stop and start replication on the replica using the STOP REPLICA | SLAVE  and START REPLICA | SLAVE  statements. From MySQL 8.0.22, STOP SLAVE  and START SLAVE  are deprecated, and STOP REPLICA  and START REPLICA  are available to use instead. 

To stop processing of the binary log from the source, use STOP REPLICA | SLAVE : 

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

When replication is stopped, the replication I/O thread stops reading events from the source binary log and writing them to the relay log, and the SQL thread stops reading events from the relay log and executing them. You can pause the I/O or SQL thread individually by specifying the thread type: 

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

To start execution again, use the START REPLICA | SLAVE  statement: 

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

To start a particular thread, specify the thread type: 

mysql> START SLAVE IO_THREAD; mysql> START SLAVE SQL_THREAD; Or from MySQL 8.0.22: mysql> START REPLICA IO_THREAD; mysql> START REPLICA SQL_THREAD; 

For a replica that performs updates only by processing events from the source, stopping only the SQL thread can be useful if you want to perform a backup or other task. The I/O thread continues to read events from the source but they are not executed. This makes it easier for the replica to catch up when you restart the SQL thread. 

