Documentation Home
MySQL Performance Schema
Related Documentation Download this Excerpt
PDF (US Ltr) - 0.9Mb
PDF (A4) - 0.9Mb
HTML Download (TGZ) - 141.5Kb
HTML Download (Zip) - 159.7Kb

MySQL Performance Schema  /  ...  /  The replication_applier_status_by_coordinator Table

10.11.5 The replication_applier_status_by_coordinator Table

For a multithreaded slave, the slave uses multiple worker threads and a coordinator thread to manage them, and this table shows the status of the coordinator thread. For a single-threaded slave, this table is empty. For a multithreaded slave, the replication_applier_status_by_worker table shows the status of the worker threads.

The replication_applier_status_by_coordinator 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 Replication Channels for more information.


    The SQL/coordinator thread ID.


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


    The error number and error message of the most recent error that caused the SQL/coordinator thread to stop. An error number of 0 and message which is an empty string means 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 Server Error Message Reference.


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

TRUNCATE TABLE is not permitted for the replication_applier_status_by_coordinator table.

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

replication_applier_status_by_coordinator Column SHOW SLAVE STATUS Column

User Comments
User comments in this section are, as the name implies, provided by MySQL users. The MySQL documentation team is not responsible for, nor do they endorse, any of the information provided here.
Sign Up Login You must be logged in to post a comment.