Rechercher dans le manuel MySQL

26.12.11.2 The replication_connection_status Table

Contents

This table shows the current status of the I/O thread that handles the slave server connection to the master server, information on the last transaction queued in the relay log, and information on the transaction currently being queued in the relay log.

Compared to the replication_connection_configuration table, replication_connection_status changes more frequently. It contains values that change during the connection, whereas replication_connection_configuration contains values which define how the slave connects to the master and that remain constant during the connection.

The replication_connection_status table has these columns:

  • CHANNEL_NAME

    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.

  • GROUP_NAME

    If this server is a member of a group, shows the name of the group the server belongs to.

  • SOURCE_UUID

    The server_uuid value from the master.

  • THREAD_ID

    The I/O thread ID.

  • SERVICE_STATE

    ON (thread exists and is active or idle), OFF (thread no longer exists), or CONNECTING (thread exists and is connecting to the master).

  • RECEIVED_TRANSACTION_SET

    The set of global transaction IDs (GTIDs) corresponding to all transactions received by this slave. Empty if GTIDs are not in use. See GTID Sets for more information.

  • LAST_ERROR_NUMBER, LAST_ERROR_MESSAGE

    The error number and error message of the most recent error that caused the I/O 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.

  • LAST_ERROR_TIMESTAMP

    A timestamp in 'YYYY-MM-DD HH:MM:SS[.fraction]' format that shows when the most recent I/O error took place.

  • LAST_HEARTBEAT_TIMESTAMP

    A timestamp in 'YYYY-MM-DD HH:MM:SS[.fraction]' format that shows when the most recent heartbeat signal was received by a replication slave.

  • COUNT_RECEIVED_HEARTBEATS

    The total number of heartbeat signals that a replication slave received since the last time it was restarted or reset, or a CHANGE MASTER TO statement was issued.

  • LAST_QUEUED_TRANSACTION

    The global transaction ID (GTID) of the last transaction that was queued to the relay log.

  • LAST_QUEUED_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP

    A timestamp in 'YYYY-MM-DD HH:MM:SS[.fraction]' format that shows when the last transaction queued in the relay log was committed on the original master.

  • LAST_QUEUED_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP

    A timestamp in 'YYYY-MM-DD HH:MM:SS[.fraction]' format that shows when the last transaction queued in the relay log was committed on the immediate master.

  • LAST_QUEUED_TRANSACTION_START_QUEUE_TIMESTAMP

    A timestamp in 'YYYY-MM-DD HH:MM:SS[.fraction]' format that shows when the last transaction was placed in the relay log queue by this I/O thread.

  • LAST_QUEUED_TRANSACTION_END_QUEUE_TIMESTAMP

    A timestamp in 'YYYY-MM-DD HH:MM:SS[.fraction]' format that shows when the last transaction was queued to the relay log files.

  • QUEUEING_TRANSACTION

    The global transaction ID (GTID) of the currently queueing transaction in the relay log.

  • QUEUEING_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP

    A timestamp in 'YYYY-MM-DD HH:MM:SS[.fraction]' format that shows when the currently queueing transaction was committed on the original master.

  • QUEUEING_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP

    A timestamp in 'YYYY-MM-DD HH:MM:SS[.fraction]' format that shows when the currently queueing transaction was committed on the immediate master.

  • QUEUEING_TRANSACTION_START_QUEUE_TIMESTAMP

    A timestamp in 'YYYY-MM-DD HH:MM:SS[.fraction]' format that shows when the first event of the currently queueing transaction was written to the relay log by this I/O thread.

When the Performance Schema is disabled, local timing information is not collected, so the fields showing the start and end timestamps for queued transactions are zero.

The replication_connection_status table has these indexes:

  • Primary key on (CHANNEL_NAME)

  • Index on (THREAD_ID)

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

replication_connection_status Column SHOW SLAVE STATUS Column
SOURCE_UUID Master_UUID
THREAD_ID None
SERVICE_STATE Slave_IO_Running
RECEIVED_TRANSACTION_SET Retrieved_Gtid_Set
LAST_ERROR_NUMBER Last_IO_Errno
LAST_ERROR_MESSAGE Last_IO_Error
LAST_ERROR_TIMESTAMP Last_IO_Error_Timestamp

Find a PHP function

Document created the 26/06/2006, last modified the 26/10/2018
Source of the printed document:https://www.gaudry.be/en/mysql-rf-replication-connection-status-table.html

The infobrol is a personal site whose content is my sole responsibility. The text is available under CreativeCommons license (BY-NC-SA). More info on the terms of use and the author.

References

  1. View the html document Language of the document:en Manuel MySQL : https://dev.mysql.com/

These references and links indicate documents consulted during the writing of this page, or which may provide additional information, but the authors of these sources can not be held responsible for the content of this page.
The author This site is solely responsible for the way in which the various concepts, and the freedoms that are taken with the reference works, are presented here. Remember that you must cross multiple source information to reduce the risk of errors.

Contents Haut