PDF (US Ltr) - 0.7Mb
Lists the Replication Master configuration metrics and provides a brief description of each.
Table 7.27 Replication Master Configuration Metrics
|Auto Increment Increment
|Controls the interval between successive column values within all AUTO_INCREMENT columns within the MySQL server.
|Auto Increment Offset
|Determines the starting point for the AUTO_INCREMENT column values within the MySQL server.
|Enforce Gtid Consistency Enabled
|Allows execution of only those statements that can be logged in a transactionally safe manner.
|Contains a representation of the set of all transactions that are logged in the binary log.
|Gtid Executed Compression Period
|Compress the mysql.gtid_executed table each time this many transactions have been processed. A setting of 0 means that this table is not compressed. Since no compression of the table occurs when using the binary log, setting the value of the variable has no effect unless binary logging is disabled.
|Shows whether GTIDs are enabled.
|Specifies whether and how the next GTID is obtained.
|Holds a list of all GTIDs along with their owners.
|The set of all transactions that have been purged from the binary log.
|The setting of this variable determines whether the slave logs master status and connection information to a FILE (master.info), or to a TABLE (mysql.slave_master_info).
|The MySQL server's UUID, this variable is only available on versions > 5.6.1.
|Semi Sync Master Enabled
|Whether semi-synchronous replication is enabled on the master MySQL server.
|Semi Sync Master Timeout
|How long the master waits on a commit (in milliseconds) for acknowledgment from a slave before timing out and reverting to asynchronous replication.
|Semi Sync Master Trace Level
|The semi-synchronous replication debug trace level on the master.
|Semi Sync Master Wait No Slave Enabled
|Whether the master waits for the timeout to expire before reverting to normal replication even if the slave count drops to zero during the timeout period.
|The server ID, used in replication to give each master and slave a unique identity.
|Verify Checksum Enabled
|Enabling this option causes the master to verify events from the binary log using checksums, and to stop with an error in the event of a mismatch.