Documentation Home
MySQL 5.7 Reference Manual
Related Documentation Download this Manual Excerpts from this Manual The replication_applier_status_by_worker Table

In MySQL 5.7.9 and later, if the slave is not multi-threaded, this table shows the status of the applier thread. (Previously, this table was empty in such cases, and this information was reported in the replication_applier_status_by_coordinator table; see Bug #74765, Bug #20001173.) Otherwise, the slave uses multiple worker threads and a coordinator thread to manage them, and this table shows the status of the worker threads. This table was added in MySQL 5.7.2 as replication_execute_status_by_worker, and renamed replication_applier_status_by_worker in MySQL 5.7.6. For a multi-threaded slave, the replication_applier_status_by_coordinator table shows the status of the coordinator thread.

The replication_applier_status_by_worker table has these columns:


    The replication channel which this row is displaying. There is always a default replication channel, and more replication channels can be added. See Section 17.2.3, “Replication Channels” for more information.


    The worker identifier (same value as the id column in the mysql.slave_worker_info table). After STOP SLAVE, the THREAD_ID column becomes NULL, but the WORKER_ID value is preserved.


    The worker thread ID.


    ON (thread exists and is active or idle) or OFF (thread no longer exists).


    The transaction that the worker has last seen. The worker has not necessarily applied this transaction because it could still be in the process of doing so.

    If the gtid_mode system variable value is OFF, this column is ANONYMOUS, indicating that transactions do not have global transaction identifiers (GTIDs) and are identified by file and position only.

    If gtid_mode is ON, the column value is defined as follows:

    • If no transaction has executed, the column is empty.

    • When a transaction has executed, the column is set from gtid_next as soon as gtid_next is set. From this moment, the column always shows a GTID.

    • The GTID is preserved until the next transaction is executed. If an error occurs, the column value is the GTID of the transaction being executed by the worker when the error occurred.

    • When the next GTID log event is picked up by this worker thread, this column is updated from gtid_next soon after gtid_next is set.


    The error number and error message of the most recent error that caused the worker thread to stop. An error number of 0 and message of the empty string mean no error. If the LAST_ERROR_MESSAGE value is not empty, the error values also appear in the slave's error log.

    Issuing RESET MASTER or RESET SLAVE resets the values shown in these columns.

    All error codes and messages displayed in the LAST_ERROR_NUMBER and LAST_ERROR_MESSAGE columns correspond to error values listed in Section B.3, “Server Error Codes and Messages”.


    A timestamp in YYMMDD HH:MM:SS format that shows when the most recent worker error occurred.

The following table shows the correspondence between replication_applier_status_by_worker columns and SHOW SLAVE STATUS columns.

replication_applier_status_by_worker ColumnSHOW SLAVE STATUS Column

Download this Manual
User Comments
Sign Up Login You must be logged in to post a comment.