Differences in dm secondsBehindMaster Values

This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: dm secondsBehindMaster数值有差异

| username: Jjjjayson_zeng

[TiDB Usage Environment] Production Environment
[TiDB Version] DM version v5.4.0
[Reproduction Path] What operations were performed when the issue occurred
[Encountered Issue: Issue Phenomenon and Impact]
[Resource Configuration]
[Attachment: Screenshot/Log/Monitoring]
I saw similar issues in other posts with version 6.5 as well.

| username: dba-kit | Original post link

Is the recent TPS 0? Is the downstream TiDB of DM under high load?

| username: Jjjjayson_zeng | Original post link

High, high for a period of time.

| username: dba-kit | Original post link

In the scenario shown in the screenshot, it is indeed the case that some binlogs have not yet been executed, and replication delay is quite normal. The strange thing is that the TPS is 0, meaning that there has been no successful write. I estimate that it is most likely not an issue with DM, but rather that the downstream TiDB has a high load, leading to a decrease in write speed.

| username: 特雷西-迈克-格雷迪 | Original post link

I had this problem a few days ago as well.

| username: 特雷西-迈克-格雷迪 | Original post link

I resolved it by using stop-task xxxx; start-task xxx;.

| username: system | Original post link

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.