SQL Statements for Controlling Replica Servers [0-9,A-F] interval : n [- n ] ( n  >= 1) 13.4.2.9 STOP REPLICA | SLAVE Statement Starts the replication threads. From MySQL 8.0.22,  START SLAVE  is deprecated and the alias  START REPLICA  should be used instead. The statement works in the same way as before, only the terminology used for the statement and its output has changed. Both versions of the statement update the same status variables when used. Please see the documentation for  START REPLICA  for a description of the statement. STOP {REPLICA | SLAVE} [ thread_types ] [ channel_option ] thread_types : [ thread_type  [,  thread_type ] ... ] thread_type : IO_THREAD | SQL_THREAD channel_option : FOR CHANNEL  channel Stops the replication threads. From MySQL 8.0.22, use  STOP REPLICA  in place of  STOP SLAVE , which is now deprecated. In releases before MySQL 8.0.22, use  STOP SLAVE . STOP REPLICA | SLAVE  requires the  REPLICATION_SLAVE_ADMIN  privilege (or the deprecated  SUPER privilege). Recommended best practice is to execute  STOP REPLICA | SLAVE  on the replica before stopping the replica server (see Section 5.1.19, “The Server Shutdown Process” , for more information). Like  START REPLICA | SLAVE , this statement may be used with the  IO_THREAD  and  SQL_THREAD options to name the replication thread or threads to be stopped. Note that the Group Replication applier channel ( group_replication_applier ) has no replication I/O thread, only a replication SQL thread. Using the  SQL_THREAD  option therefore stops this channel completely. STOP REPLICA | SLAVE  causes an implicit commit of an ongoing transaction. See Section 13.3.3, “Statements That Cause an Implicit Commit” . gtid_next  must be set to  AUTOMATIC  before issuing this statement. You can control how long  STOP REPLICA | SLAVE  waits before timing out by setting the rpl_stop_slave_timeout  system variable. This can be used to avoid deadlocks between  STOP REPLICA | SLAVE  and other SQL statements using different client connections to the replica. When the timeout value is reached, the issuing client returns an error message and stops waiting, but the  STOP REPLICA | SLAVE  instruction remains in effect. Once the replication threads are no longer busy, the STOP REPLICA | SLAVE  statement is executed and the replica stops. Some  CHANGE REPLICATION SOURCE TO  |  CHANGE MASTER TO  statements are allowed while the replica is running, depending on the states of the replication threads. However, using  STOP REPLICA | SLAVE  prior to executing a  CHANGE REPLICATION SOURCE TO  |  CHANGE MASTER TO  statement in such cases is still supported. See Section 13.4.2.3, “CHANGE REPLICATION SOURCE TO Statement” , Section 13.4.2.1, “CHANGE MASTER TO Statement” , and Section 17.4.8, “Switching Sources During Failover” , for more information. The optional  FOR CHANNEL  channel  clause enables you to name which replication channel the statement applies to. Providing a  FOR CHANNEL  channel  clause applies the  STOP REPLICA | SLAVE statement to a specific replication channel. If no channel is named and no extra channels exist, the 2780