Last_Error: Cannot execute the current event group in the parallel mode. Encountered event Gtid, relay-log name {目錄}/relaylog/mysql-relay.000002,position 280408 which prevents execution of this event group in parallel mode. Reason: The master event is logically timestamped incorrectly..
……
Last_IO_Errno: 0
Last_IO_Error:
Last_SQL_Errno: 1755
Last_SQL_Error: Cannot execute the current event group in the parallel mode. Encountered event Gtid, relay-log name {目錄}/relaylog/mysql-relay.000002,position 280408 which prevents execution of this event group in parallel mode. Reason: The master event is logically timestamped incorrectly..
Replicate_Ignore_Server_Ids:
……
錯誤提示很明顯： Cannot execute the current event group in the parallel mode 不能在parallel模式下執行目前的這個event組
在5.6作為slave也有可能遇到這個問題。
錯誤提示和原因顯示很明白，關掉并行復制就可以了：
STOP SLAVE;
SET GLOBAL slave_parallel_workers=0;
START SLAVE;
同樣是1755報錯，目前收集到日志中可能給出的reason有下面三個：
① Reason：The master event is logically timestamped incorrectly（這個可能也和在5.7上設置slave_parallel_type="LOGICAL_CLOCK"有關）
② Reason: possible malformed group of events from an old master
③ Reason：the events is a part of a group that is unsupported in the parallel execution mode.
Last_Error: … The slave coordinator and worker threads are stopped, possibly leaving data in inconsistent state. A restart should restore consistency automatically, although using non-transactional storage for data or info tables or DDL queries could lead to problems.In such cases you have to examine your data (see documentation for details).
……
Last_SQL_Errno: 1756
Last_SQL_Error: … The slave coordinator and worker threads are stopped, possibly leaving data in inconsistent state. A restart should restore consistency automatically, although using non-transactional storage for data or info tables or DDL queries could lead to problems.In such cases you have to examine your data (see documentation for details).
