- 184.108.40.206 The replication_connection_configuration Table
- 220.127.116.11 The replication_connection_status Table
- 18.104.22.168 The replication_asynchronous_connection_failover Table
- 22.214.171.124 The replication_asynchronous_connection_failover_managed Table
- 126.96.36.199 The replication_applier_configuration Table
- 188.8.131.52 The replication_applier_status Table
- 184.108.40.206 The replication_applier_status_by_coordinator Table
- 220.127.116.11 The replication_applier_status_by_worker Table
- 18.104.22.168 The replication_applier_global_filters Table
- 22.214.171.124 The replication_applier_filters Table
- 126.96.36.199 The replication_group_members Table
- 188.8.131.52 The replication_group_member_stats Table
- 184.108.40.206 The replication_group_member_actions Table
- 220.127.116.11 The replication_group_configuration_version Table
- 18.104.22.168 The replication_group_communication_information Table
- 22.214.171.124 The binary_log_transaction_compression_stats Table
The Performance Schema provides tables that expose replication
information. This is similar to the information available from
REPLICA STATUS statement, but representation in table
form is more accessible and has usability benefits:
SHOW REPLICA STATUSoutput is useful for visual inspection, but not so much for programmatic use. By contrast, using the Performance Schema tables, information about replica status can be searched using general
SELECTqueries, including complex
WHEREconditions, joins, and so forth.
Query results can be saved in tables for further analysis, or assigned to variables and thus used in stored procedures.
The replication tables provide better diagnostic information. For multithreaded replica operation,
SHOW REPLICA STATUSreports all coordinator and worker thread errors using the
Last_SQL_Errorfields, so only the most recent of those errors is visible and information can be lost. The replication tables store errors on a per-thread basis without loss of information.
The last seen transaction is visible in the replication tables on a per-worker basis. This is information not avilable from
SHOW REPLICA STATUS.
Developers familiar with the Performance Schema interface can extend the replication tables to provide additional information by adding rows to the tables.
The Performance Schema provides the following replication-related tables:
Tables that contain information about the connection of the replica to the source:
Tables that contain general (not thread-specific) information about the transaction applier:
Tables that contain information about specific threads responsible for applying transactions received from the source:
Tables that contain information about channel based replication filters:
Tables that contain information about Group Replication members:
For more information see Section 18.4, “Monitoring Group Replication”.
The following Performance Schema replication tables continue to be populated when the Performance Schema is disabled:
The exception is local timing information (start and end
timestamps for transactions) in the replication tables
This information is not collected when the Performance Schema is
The following sections describe each replication table in more
detail, including the correspondence between the columns
REPLICA STATUS and the replication table columns in
which the same information appears.
The remainder of this introduction to the replication tables
describes how the Performance Schema populates them and which
REPLICA STATUS are not represented in the tables.
The Performance Schema populates the replication tables as follows:
CHANGE REPLICATION SOURCE TO|
CHANGE MASTER TO, the configuration parameters can be seen in the tables. At this time, there are no active replication threads, so the
SERVICE_STATEcolumns have a value of
START REPLICA(or before MySQL 8.0.22,
START SLAVE), non-
THREAD_IDvalues can be seen. Threads that are idle or active have a
ON. The thread that connects to the source has a value of
CONNECTINGwhile it establishes the connection, and
ONthereafter as long as the connection lasts.
STOP REPLICA, the
SERVICE_STATEcolumns for threads that no longer exist have a value of
The tables are preserved after
STOP REPLICAor threads stopping due to an error.
replication_applier_status_by_workertable is nonempty only when the replica is operating in multithreaded mode. That is, if the
slave_parallel_workerssystem variable is greater than 0, this table is populated when
START REPLICAis executed, and the number of rows shows the number of workers.
The information in the Performance Schema replication tables
differs somewhat from the information available from
REPLICA STATUS because the tables are oriented toward
use of global transaction identifiers (GTIDs), not file names
and positions, and they represent server UUID values, not server
ID values. Due to these differences, several
REPLICA STATUS columns are not preserved in the
Performance Schema replication tables, or are represented a
The following fields refer to file names and positions and are not preserved:
Master_Log_File Read_Master_Log_Pos Relay_Log_File Relay_Log_Pos Relay_Master_Log_File Exec_Master_Log_Pos Until_Condition Until_Log_File Until_Log_Pos
Master_Info_Filefield is not preserved. It refers to the
master.infofile used for the replica's source metadata repository, which has been superseded by the use of crash-safe tables for the repository.
Skip_Counterfield is based on event counts, not GTIDs, and is not preserved.
These error fields are aliases for
Last_SQL_Error, so they are not preserved:
In the Performance Schema, this error information is available in the
LAST_ERROR_MESSAGEcolumns of the
replication_applier_status_by_coordinatorif the replica is multithreaded). Those tables provide more specific per-thread error information than is available from
Fields that provide information about command-line filtering options is not preserved:
Replicate_Do_DB Replicate_Ignore_DB Replicate_Do_Table Replicate_Ignore_Table Replicate_Wild_Do_Table Replicate_Wild_Ignore_Table
Replica_SQL_Running_Statefields are not preserved. If needed, these values can be obtained from the process list by using the
THREAD_IDcolumn of the appropriate replication table and joining it with the
IDcolumn in the
PROCESSLISTtable to select the
STATEcolumn of the latter table.
Executed_Gtid_Setfield can show a large set with a great deal of text. Instead, the Performance Schema tables show GTIDs of transactions that are currently being applied by the replica. Alternatively, the set of executed GTIDs can be obtained from the value of the
Relay_Log_Spacefields are in to-be-decided status and are not preserved.
The first column of the replication Performance Schema tables is
CHANNEL_NAME. This enables the tables to be
viewed per replication channel. In a non-multisource replication
setup there is a single default replication channel. When you
are using multiple replication channels on a replica, you can
filter the tables per replication channel to monitor a specific
replication channel. See Section 17.2.2, “Replication Channels”
and Section 126.96.36.199, “Monitoring Multi-Source Replication” for