Rechercher dans le manuel MySQL
26.12.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. This table
provides information about the last transaction which was
buffered by the coordinator thread to a worker’s queue, as
well as the transaction it is currently buffering. The start
timestamp refers to when this thread read the first event of
the transaction from the relay log to buffer it to a
worker’s queue, while the end timestamp refers to when the
last event finished buffering to the worker’s queue.
The
replication_applier_status_by_coordinator
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.
THREAD_ID
The SQL/coordinator thread ID.
SERVICE_STATE
ON
(thread exists and is active or idle) orOFF
(thread no longer exists).LAST_ERROR_NUMBER
,LAST_ERROR_MESSAGE
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
orRESET SLAVE
resets the values shown in these columns.All error codes and messages displayed in the
LAST_ERROR_NUMBER
andLAST_ERROR_MESSAGE
columns correspond to error values listed in Section B.3.1, “Server Error Message Reference”.LAST_ERROR_TIMESTAMP
A timestamp in
'
format that shows when the most recent SQL/coordinator error occurred.YYYY-MM-DD hh:mm:ss
[.fraction
]'LAST_PROCESSED_TRANSACTION
The global transaction ID (GTID) of the last transaction processed by this coordinator.
LAST_PROCESSED_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP
A timestamp in
'
format that shows when the last transaction processed by this coordinator was committed on the original master.YYYY-MM-DD hh:mm:ss
[.fraction
]'LAST_PROCESSED_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP
A timestamp in
'
format that shows when the last transaction processed by this coordinator was committed on the immediate master.YYYY-MM-DD hh:mm:ss
[.fraction
]'LAST_PROCESSED_TRANSACTION_START_BUFFER_TIMESTAMP
A timestamp in
'
format that shows when this coordinator thread started writing the last transaction to the buffer of a worker thread.YYYY-MM-DD hh:mm:ss
[.fraction
]'LAST_PROCESSED_TRANSACTION_END_BUFFER_TIMESTAMP
A timestamp in
'
format that shows when the last transaction was written to the buffer of a worker thread by this coordinator thread.YYYY-MM-DD hh:mm:ss
[.fraction
]'PROCESSING_TRANSACTION
The global transaction ID (GTID) of the transaction that this coordinator thread is currently processing.
PROCESSING_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP
A timestamp in
'
format that shows when the currently processing transaction was committed on the original master.YYYY-MM-DD hh:mm:ss
[.fraction
]'PROCESSING_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP
A timestamp in
'
format that shows when the currently processing transaction was committed on the immediate master.YYYY-MM-DD hh:mm:ss
[.fraction
]'PROCESSING_TRANSACTION_START_BUFFER_TIMESTAMP
A timestamp in
'
format that shows when this coordinator thread started writing the currently processing transaction to the buffer of a worker thread.YYYY-MM-DD hh:mm:ss
[.fraction
]'
When the Performance Schema is disabled, local timing information is not collected, so the fields showing the start and end timestamps for buffered transactions are zero.
The
replication_applier_status_by_coordinator
table has these indexes:
Primary key on (
CHANNEL_NAME
)Index on (
THREAD_ID
)
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 |
---|---|
THREAD_ID |
None |
SERVICE_STATE |
Slave_SQL_Running |
LAST_ERROR_NUMBER |
Last_SQL_Errno |
LAST_ERROR_MESSAGE |
Last_SQL_Error |
LAST_ERROR_TIMESTAMP |
Last_SQL_Error_Timestamp |
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-applier-status-by-coordinator-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
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.