SHOW SLAVE STATUS output is useful for visual inspection, but not so much for programmatic use. By contrast, using the Performance Schema tables, information about slave status can be searched using general SELECT queries, including complex WHERE conditions, 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 slave operation, SHOW SLAVE STATUS reports all coordinator and worker thread errors using the Last_SQL_Errno and Last_SQL_Error fields, 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 SLAVE STATUS.

Developers familiar with the Performance Schema interface can extend the replication tables to provide additional information by adding rows to the tables.

Tables that contain information about the connection of the slave server to the master server:

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 master:

Tables that contain information about channel based replication filters:

Tables that contain information about Group Replication members:

For more information see Section 18.3, “Monitoring Group Replication”.

replication_connection_configuration

replication_connection_status

replication_applier_configuration

replication_applier_status

replication_applier_status_by_coordinator

replication_applier_status_by_worker

Prior to execution of CHANGE MASTER TO, the tables are empty.

After CHANGE MASTER TO, the configuration parameters can be seen in the tables. At this time, there are no active slave threads, so the THREAD_ID columns are NULL and the SERVICE_STATE columns have a value of OFF.

After START SLAVE, non-NULL THREAD_ID values can be seen. Threads that are idle or active have a SERVICE_STATE value of ON. The thread that connects to the master server has a value of CONNECTING while it establishes the connection, and ON thereafter as long as the connection lasts.

After STOP SLAVE, the THREAD_ID columns become NULL and the SERVICE_STATE columns for threads that no longer exist have a value of OFF.

The tables are preserved after STOP SLAVE or threads dying due to an error.

The replication_applier_status_by_worker table is nonempty only when the slave is operating in multithreaded mode. That is, if the slave_parallel_workers system variable is greater than 0, this table is populated when START SLAVE is executed, and the number of rows shows the number of workers.

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

The Master_Info_File field is not preserved. It refers to the master.info file used for the slave's master info repository, which has been superseded by crash-safe slave tables.

The following fields are based on server_id, not server_uuid, and are not preserved:

Master_Server_Id
Replicate_Ignore_Server_Ids

The Skip_Counter field is based on event counts, not GTIDs, and is not preserved.

These error fields are aliases for Last_SQL_Errno and Last_SQL_Error, so they are not preserved:

Last_Errno
Last_Error

In the Performance Schema, this error information is available in the LAST_ERROR_NUMBER and LAST_ERROR_MESSAGE columns of the replication_applier_status_by_coordinator table (and replication_applier_status_by_worker if the slave is multithreaded). Those tables provide more specific per-thread error information than is available from Last_Errno and Last_Error.

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

The Slave_IO_State and Slave_SQL_Running_State fields are not preserved. If needed, these values can be obtained from the process list by using the THREAD_ID column of the appropriate replication table and joining it with the ID column in the INFORMATION_SCHEMA PROCESSLIST table to select the STATE column of the latter table.

The Executed_Gtid_Set field 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 slave. Alternatively, the set of executed GTIDs can be obtained from the value of the gtid_executed system variable.

The Seconds_Behind_Master and Relay_Log_Space fields are in to-be-decided status and are not preserved.

Slave_retried_transactions

Slave_last_heartbeat

Slave_received_heartbeats

Slave_heartbeat_period

Slave_running