SHOW Statements MySQL to replicate  TIMESTAMP  successfully. However, the problem for  Seconds_Behind_Source is that if M1 also receives direct updates from clients, the  Seconds_Behind_Source  value randomly fluctuates because sometimes the last event from M1 originates from M0 and sometimes is the result of a direct update on M1. When using a multithreaded replica, you should keep in mind that this value is based on Exec_Source_Log_Pos , and so may not reflect the position of the most recently committed transaction. The error number and error message of the most recent error that caused the replication I/O thread to stop. An error number of 0 and message of the empty string mean “no error.”  If the  Last_IO_Error value is not empty, the error values also appear in the replica’s error log. I/O error information includes a timestamp showing when the most recent I/O thread error occurred. This timestamp uses the format  YYMMDD hh:mm:ss , and appears in the  Last_IO_Error_Timestamp column. The error number and error message of the most recent error that caused the replication SQL thread to stop. An error number of 0 and message of the empty string mean “no error.”  If the  Last_SQL_Error value is not empty, the error values also appear in the replica’s error log. Issuing  RESET MASTER  or  RESET REPLICA | SLAVE  resets the values shown in these columns. If the replica is multithreaded, the replication SQL thread is the coordinator for worker threads. In this case, the  Last_SQL_Error  field shows exactly what the  Last_Error_Message  column in the Performance Schema  replication_applier_status_by_coordinator  table shows. The field value is modified to suggest that there may be more failures in the other worker threads which can be seen in the  replication_applier_status_by_worker  table that shows each worker thread’s status. If that table is not available, the replica error log can be used. The log or the replication_applier_status_by_worker  table should also be used to learn more about the failure shown by  SHOW REPLICA | SLAVE STATUS  or the coordinator table. SQL error information includes a timestamp showing when the most recent SQL thread error occurred. This timestamp uses the format  YYMMDD hh:mm:ss , and appears in the Last_SQL_Error_Timestamp  column. Issuing  RESET MASTER  or  RESET REPLICA | SLAVE  resets the values shown in these columns. In MySQL 8.0, all error codes and messages displayed in the  Last_SQL_Errno  and  Last_SQL_Error columns correspond to error values listed in Server Error Message Reference. This was not always true in previous versions. (Bug #11760365, Bug #52768) Any server IDs that have been specified using the  IGNORE_SERVER_IDS  option of the  CHANGE REPLICATION SOURCE TO  |  CHANGE MASTER TO  statement, so that the replica ignores events from these servers. This option is used in a circular or other multi-source replication setup when one of the • Replicate_Ignore_Server_Ids 2954 • Last_SQL_Errno ,  Last_SQL_Error • Last_IO_Errno ,  Last_IO_Error