This table shows the current general transaction execution
status on the replica. The table provides information about
general aspects of transaction applier status that are not
specific to any thread involved. Thread-specific status
information is available in the
replication_applier_status_by_coordinator
table (and
replication_applier_status_by_worker
if the replica is multithreaded).
The replication_applier_status
table has these columns:
CHANNEL_NAMEThe replication channel which this row is displaying. There is always a default replication channel, and more replication channels can be added. See Replication Channels for more information.
SERVICE_STATEShows
ONwhen the replication channel's applier threads are active or idle,OFFmeans that the applier threads are not active.REMAINING_DELAYIf the replica is waiting for
DESIRED_DELAYseconds to pass since the source applied an event, this field contains the number of delay seconds remaining. At other times, this field isNULL. (TheDESIRED_DELAYvalue is stored in thereplication_applier_configurationtable.)COUNT_TRANSACTIONS_RETRIESShows the number of retries that were made because the replication SQL thread failed to apply a transaction. The maximum number of retries for a given transaction is set by the
slave_transaction_retriessystem variable.
TRUNCATE TABLE is not permitted
for the
replication_applier_status table.
The following table shows the correspondence between
replication_applier_status
columns and SHOW SLAVE STATUS
columns.
replication_applier_status Column |
SHOW SLAVE STATUS Column |
|---|---|
SERVICE_STATE |
None |
REMAINING_DELAY |
SQL_Remaining_Delay |