content_image/771070.jpg content_image/771071.jpg content_image/771072.jpg
<img src='content_image/771070.jpg'>

The semisynchronous replication debug trace level on the replica server. See rpl_semi_sync_master_trace_level  for the permissible values. 

This variable is available only if the replica-side semisynchronous replication plugin is installed. 

• rpl_stop_slave_timeout 

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

You can control the length of time (in seconds) that STOP REPLICA | SLAVE  waits before timing out by setting this variable. This can be used to avoid deadlocks between STOP REPLICA | SLAVE  and other SQL statements using different client connections to the replica. 

The maximum and default value of rpl_stop_slave_timeout  is 31536000 seconds (1 year). The minimum is 2 seconds. Changes to this variable take effect for subsequent STOP REPLICA | SLAVE statements. 

This variable affects only the client that issues a STOP REPLICA | SLAVE  statement. When the timeout is reached, the issuing client returns an error message stating that the command execution is incomplete. The client then stops waiting for the replication I/O and SQL threads to stop, but the replication threads continue to try to stop, and 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. 

• skip_slave_start 

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

Tells the replica server not to start the replication I/O and SQL threads when the server starts. To start the threads later, use a START REPLICA | SLAVE  statement. 

This system variable is available from MySQL 8.0.24. It is read-only and can be set by using the PERSIST_ONLY  keyword or the @@persist_only  qualifier with the SET  statement. The --skip- 

