DM Enabling Relay Log Not Effective

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

Original topic: DM 开启relay log 不生效

| username: TiDBer_yyy

[TiDB Usage Environment] Test
[DM Version] 2.0.7
Enable relay: The worker machine is consistent with the source worker. Found that relay log is not started: "relayStatus": null

» query-status -s mysql-expertise_stattax_sbtest
{
    "result": true,
    "msg": "",
    "sources": [
        {
            "result": true,
            "msg": "no sub task started",
            "sourceStatus": {
                "source": "mysql-expertise_stattax_sbtest",
                "worker": "dm-192.168.22.7-8263",
                "result": null,
                "relayStatus": null
            },
            "subTaskStatus": [
            ]
        }
    ]
}
» start-relay  -s mysql-expertise_stattax_sbtest dm-192.168.22.7-8263
{
    "result": true,
    "msg": ""
}
» query-status -s mysql-expertise_stattax_sbtest
{
    "result": true,
    "msg": "",
    "sources": [
        {
            "result": true,
            "msg": "no sub task started",
            "sourceStatus": {
                "source": "mysql-expertise_stattax_sbtest",
                "worker": "dm-192.168.22.7-8263",
                "result": null,
                "relayStatus": null
            },
            "subTaskStatus": [
            ]
        }
    ]
}

Found on the official website: Two workers were started. Local test started two, only one relay log could be started successfully (official website started two relay logs).

| username: TiDBer_yyy | Original post link

After destroying and rebuilding the DM cluster, it can succeed :rofl:

| username: Anna | Original post link

Refer to this: DM 任务完整配置文件介绍 | PingCAP 文档中心

| username: system | Original post link

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