content_image/771497.jpg content_image/771498.jpg content_image/771493.jpg content_image/771499.jpg
be executed; after that, the replication SQL thread does not receive any more events, just as if the network connection from the source were cut. The replication SQL thread continues to run, and the output from SHOW REPLICA | SLAVE STATUS  displays Yes  in both the Replica_IO_Running  and the Replica_SQL_Running  columns, but no further events are read from the relay log. 

• --disconnect-slave-event-count 

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

## System Variables Used on Replica Servers 

The following list describes system variables for controlling replica servers. They can be set at server startup and some of them can be changed at runtime using SET . Server options used with replicas are listed earlier in this section. 

• init_slave 

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

This variable is similar to init_connect , but is a string to be executed by a replica server each time the replication SQL thread starts. The format of the string is the same as for the init_connect variable. The setting of this variable takes effect for subsequent START REPLICA | SLAVE  statements. 

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

• log_slow_slave_statements 

Note 

The replication SQL thread sends an acknowledgment to the client before it executes init_slave . Therefore, it is not guaranteed that init_slave  has been executed when START REPLICA | SLAVE  returns. See Section 13.4.2.7, “START REPLICA | SLAVE Statement”  for more information. 

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

When the slow query log is enabled, this variable enables logging for queries that have taken more than long_query_time  seconds to execute on the replica. Note that if row-based replication is in use 

