问题描述
最近突然发现mysql 从库error log里面大量报错如下
[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.
由于写入了大量的这种warning报错,从而导致errorlog体积暴增,截图如下
[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.

解决方案
经过查询文档发现这个报错是一个时间戳的bug,但是如何解决暴增的问题呢?
首先由于这个是报错是waring级别,

本文介绍了解决MySQL 8.0版本中因特定警告导致Error Log文件体积异常增长的方法。通过调整log_error_verbosity参数及利用log_error_suppression_list参数抑制指定警告信息的记录。

713

被折叠的 条评论
为什么被折叠?



