content_image/668740.jpg content_image/668742.jpg content_image/668745.jpg
value and there are multiple replication channels configured, the START REPLICA | SLAVE  statement can only be used with the FOR CHANNEL channel  clause. 

This option is incompatible with GTID-based replication, and must not be set to a nonzero value when gtid_mode=ON  is set. If you need to skip transactions when employing GTIDs, use gtid_executed from the source instead. If you have enabled GTID assignment on a replication channel using the ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS  option of the CHANGE REPLICATION SOURCE TO statement, sql_slave_skip_counter  is available. See Section 17.1.7.3, “Skipping Transactions” . 

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

• sync_master_info 

## Important 

If skipping the number of events specified by setting this variable would cause the replica to begin in the middle of an event group, the replica continues to skip until it finds the beginning of the next event group and begins from that point. For more information, see Section 17.1.7.3, “Skipping Transactions” . 

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

The number of events after which the replica updates the connection metadata repository. When the connection metadata repository is stored as an InnoDB  table, which is the default from MySQL 8.0, it is updated after this number of events. If the connection metadata repository is stored as a file, which is deprecated from MySQL 8.0, the replica synchronizes its master.info  file to disk (using fdatasync() ) after this number of events. The default value is 10000, and a zero value means that the repository is never updated. Setting this variable takes effect for all replication channels immediately, including running channels. 

• sync_relay_log 

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

