Version sans cache

Mise en cache désactivé. Réglage défaut pour cette page : actif (code DEF204)
Si l'affichage est trop lent, vous pouvez désactiver le mode utilisateur pour visualiser la version en cache.

Rechercher dans le manuel MySQL

26.12.11.2 The replication_connection_status Table

Table des matières

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

Rechercher dans le manuel MySQL

Traduction non disponible

Le manuel MySQL n'est pas encore traduit en français sur l'infobrol. Seule la version anglaise est disponible pour l'instant.

Document créé le 26/06/2006, dernière modification le 26/10/2018
Source du document imprimé : https://www.gaudry.be/mysql-rf-replication-connection-status-table.html

L'infobrol est un site personnel dont le contenu n'engage que moi. Le texte est mis à disposition sous licence CreativeCommons(BY-NC-SA). Plus d'info sur les conditions d'utilisation et sur l'auteur.

Références

  1. Consulter le document html Langue du document :en Manuel MySQL : https://dev.mysql.com/

Ces références et liens indiquent des documents consultés lors de la rédaction de cette page, ou qui peuvent apporter un complément d'information, mais les auteurs de ces sources ne peuvent être tenus responsables du contenu de cette page.
L'auteur de ce site est seul responsable de la manière dont sont présentés ici les différents concepts, et des libertés qui sont prises avec les ouvrages de référence. N'oubliez pas que vous devez croiser les informations de sources multiples afin de diminuer les risques d'erreurs.

Table des matières Haut