Rechercher dans le manuel MySQL

26.12.11.2 The replication_connection_status Table

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

Zoek in de MySQL-handleiding

Nederlandse vertaling

U hebt gevraagd om deze site in het Nederlands te bezoeken. Voor nu wordt alleen de interface vertaald, maar nog niet alle inhoud.

Als je me wilt helpen met vertalingen, is je bijdrage welkom. Het enige dat u hoeft te doen, is u op de site registreren en mij een bericht sturen waarin u wordt gevraagd om u toe te voegen aan de groep vertalers, zodat u de gewenste pagina's kunt vertalen. Een link onderaan elke vertaalde pagina geeft aan dat u de vertaler bent en heeft een link naar uw profiel.

Bij voorbaat dank.

Document heeft de 26/06/2006 gemaakt, de laatste keer de 26/10/2018 gewijzigd
Bron van het afgedrukte document:https://www.gaudry.be/nl/mysql-rf-replication-connection-status-table.html

De infobrol is een persoonlijke site waarvan de inhoud uitsluitend mijn verantwoordelijkheid is. De tekst is beschikbaar onder CreativeCommons-licentie (BY-NC-SA). Meer info op de gebruiksvoorwaarden en de auteur.

Referenties

  1. Bekijk - html-document Taal van het document:en Manuel MySQL : https://dev.mysql.com/

Deze verwijzingen en links verwijzen naar documenten die geraadpleegd zijn tijdens het schrijven van deze pagina, of die aanvullende informatie kunnen geven, maar de auteurs van deze bronnen kunnen niet verantwoordelijk worden gehouden voor de inhoud van deze pagina.
De auteur Deze site is als enige verantwoordelijk voor de manier waarop de verschillende concepten, en de vrijheden die met de referentiewerken worden genomen, hier worden gepresenteerd. Vergeet niet dat u meerdere broninformatie moet doorgeven om het risico op fouten te verkleinen.

Inhoudsopgave Haut