golang mysql时间戳_mysql-无效的复制时间戳

我已经在同一局域网中的两台Windows机器上运行的两个mysql服务器(v8.0.12)之间设置了主-主复制。

到目前为止，复制似乎工作正常。但是，存在一个问题：错误日志中填充了以下条目：

2019-07-04T11:17:54.694565+01:00 5 [Warning] [MY-010956] [Server] Invalid replication timestamps: original commit timestamp is more recent than the immediate commit timestamp. This may be an issue if delayed replication is active. Make sure that servers have their clocks set to the correct time. No further message will be emitted until after timestamps become valid again.

2019-07-04T11:17:54.696796+01:00 5 [Warning] [MY-010957] [Server] The replication timestamps have returned to normal values.

2019-07-04T11:17:54.702435+01:00 5 [Warning] [MY-010956] [Server] Invalid replication timestamps: original commit timestamp is more recent than the immediate commit timestamp. This may be an issue if delayed replication is active. Make sure that servers have their clocks set to the correct time. No further message will be emitted until after timestamps become valid again.

2019-07-04T11:17:54.704768+01:00 5 [Warning] [MY-010957] [Server] The replication timestamps have returned to normal values.

2019-07-04T11:17:54.711469+01:00 5 [Warning] [MY-010956] [Server] Invalid replication timestamps: original commit timestamp is more recent than the immediate commit timestamp. This may be an issue if delayed replication is active. Make sure that servers have their clocks set to the correct time. No further message will be emitted until after timestamps become valid again.

2019-07-04T11:17:54.713675+01:00 5 [Warning] [MY-010957] [Server] The replication timestamps have returned to normal values.

2019-07-04T11:17:54.716626+01:00 5 [Warning] [MY-010956] [Server] Invalid replication timestamps: original commit timestamp is more recent than the immediate commit timestamp. This may be an issue if delayed replication is active. Make sure that servers have their clocks set to the correct time. No further message will be emitted until after timestamps become valid again.

2019-07-04T11:17:54.718956+01:00 5 [Warning] [MY-010957] [Server] The replication timestamps have returned to normal values.

Server 1 acts as windows time-server for Server 2, and as far as I can see both servers have the same time (and timezone of course). As they are in the same LAN, there is no obvious network lag between them (ping < 1ms).

@@global.time_zone variable returns 'SYSTEM'. However, I've not set any timezone in the my.ini file.

SELECT TIMEDIFF(NOW(), UTC_TIMESTAMP) returns '02:00:00'.

I've NOT setup any replication delay, because I'm interested in a fast propagation of changes.

我非常绝望，因为错误日志在一个月的时间内会填满大于5 GB的大小。

有谁知道如何进一步分析问题(例如，任何显示当前时间延迟的mysql内部表)？

谢谢你的提示，狮子座