Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.Original topic: dm同步任务经常中断
The dm-worker_stdout.log logs this message every few minutes, what’s going on?
Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.Original topic: dm同步任务经常中断
The dm-worker_stdout.log logs this message every few minutes, what’s going on?
Does the upstream MySQL have a scheduled “abnormal” connection kill?
Later, I found the cause. It was due to frequent data modifications in the upstream database, possibly because the DM buffer was insufficient. It has been fixed now.
The status is normal, but the binlog drift point is not keeping up with the upstream. This was caused by frequent data modifications upstream and has been fixed.
You can see frequent delete and insert statements being logged in the dm-worker.log file.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.