SQL Statements for Controlling Replica Servers in the warning message  ER_FOUND_MISSING_GTIDS . Also, if during the exchange of transactions it is found that the replica has recorded or committed transactions with the source’s UUID in the GTID, but the source itself has not committed them, the source sends the error ER_SLAVE_HAS_MORE_GTIDS_THAN_MASTER  to the replica and replication does not start. For information on how to handle these situations, see Section 17.1.3.3, “GTID Auto-Positioning” . You can see whether replication is running with GTID auto- positioning enabled by checking the Performance Schema replication_connection_status  table or the output of  SHOW REPLICA STATUS . Disabling the  MASTER_AUTO_POSITION  option again makes the replica revert to file-based replication. Determines which of the replica’s network interfaces is chosen for connecting to the source, for use on replicas that have multiple network interfaces. The address configured with this option, if any, can be seen in the  Master_Bind  column of the output from  SHOW REPLICA | SLAVE STATUS . In the source metadata repository table  mysql.slave_master_info , the value can be seen as the Master_bind  column. The ability to bind a replica to a specific network interface is also supported by NDB Cluster. Specifies the interval between the reconnection attempts that the replica makes after the connection to the source times out. The attempts are limited by the  MASTER_RETRY_COUNT  option. If both the default settings are used, the replica waits 60 seconds between reconnection attempts ( MASTER_CONNECT_RETRY=60 ), and keeps attempting to reconnect at this rate for 60 days ( MASTER_RETRY_COUNT=86400 ). These values are recorded in the source metadata repository and shown in the Binary log transaction compression (available as of MySQL 8.0.20), which is activated by the  binlog_transaction_compression system variable, can also be used to save bandwidth. If you do this in combination with connection compression, connection compression has less opportunity to act on the data, but can still compress headers and those events and transaction payloads that are uncompressed. For more information on binary log transaction compression, see Section 5.4.4.5, “Binary Log Transaction Compression” . MASTER_COMPRESSION_ALGORITHMS Specifies the permitted compression algorithms for connections to the replication source server. The available algorithms are the same as for the  protocol_compression_algorithms system variable. The default value is  uncompressed . MASTER_COMPRESSION_ALGORITHMS  is available as of MySQL 8.0.18. The value of  MASTER_COMPRESSION_ALGORITHMS  applies only if the  slave_compressed_protocol  system variable is disabled. If slave_compressed_protocol  is enabled, it takes precedence over MASTER_COMPRESSION_ALGORITHMS  and connections to the source use  zlib  compression if both source and replica support that algorithm. For more information, see Section 4.2.8, “Connection Compression Control” . MASTER_CONNECT_RETRY 2749 MASTER_BIND