content_image/690831.jpg
A timestamp in ’ YYYY-MM-DD hh:mm:ss [. fraction ]’  format that shows when the last transaction processed by this coordinator was committed on the immediate source. 

• LAST_PROCESSED_TRANSACTION_START_BUFFER_TIMESTAMP 

A timestamp in ’ YYYY-MM-DD hh:mm:ss [. fraction ]’  format that shows when this coordinator thread started writing the last transaction to the buffer of a worker thread. 

• LAST_PROCESSED_TRANSACTION_END_BUFFER_TIMESTAMP 

A timestamp in ’ YYYY-MM-DD hh:mm:ss [. fraction ]’  format that shows when the last transaction was written to the buffer of a worker thread by this coordinator thread. 

• 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 ’ YYYY-MM-DD hh:mm:ss [. fraction ]’  format that shows when the currently processing transaction was committed on the original source. 

• PROCESSING_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP 

A timestamp in ’ YYYY-MM-DD hh:mm:ss [. fraction ]’  format that shows when the currently processing transaction was committed on the immediate source. 

• PROCESSING_TRANSACTION_START_BUFFER_TIMESTAMP 

A timestamp in ’ YYYY-MM-DD hh:mm:ss [. fraction ]’  format that shows when this coordinator thread started writing the currently processing transaction to the buffer of a worker thread. 

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 REPLICA | SLAVE STATUS columns. 

<img src='content_image/690831.jpg'>

## 27.12.11.8 The replication_applier_status_by_worker Table 

