dm6.6.0，tidb6.1.2，从mysql同步数据异常

🪐 TiDB 技术问题 部署&运维管理
1

【 TiDB 使用环境】生产环境
【 TiDB 版本】6.1.2
【复现路径】使用tidb把生产库的分库分表合并到同库同表
【遇到的问题：mysql中的新数据没有同步到tidb中来
【资源配置】mysql新数据没有同步到tidb，每次都是stop-task后，删除dm_meta库后再重新start-task后，新的数据才会同步过来
使用query-status查看状态，都是Running的，但是有一些日志：
“unsynced”: [
“this DM-worker doesn’t receive any shard DDL of this group”

包括用shard-ddl-lock查看锁，有好多个锁，使用shard-ddl-lock unlock 又提示lock-id不存在

2

1、把task 配置发下
2、把完整的query-status内容发下
3、是否是分库分表合并场景？

4

query-status输出.txt (37.6 KB)

2、补充query-status输出

5

$ tiup dmctl --master-addr 127.0.0.1:8261 shard-ddl-lock ai
tiup is checking updates for component dmctl …
Starting component dmctl: /home/tidb/.tiup/components/dmctl/v6.6.0/dmctl/dmctl --master-addr 127.0.0.1:8261 shard-ddl-lock ai
{
“result”: true,
“msg”: “”,
“locks”: [
{
“ID”: “ai-scriptDraft.t_push”,
“task”: “ai”,
“mode”: “pessimistic”,
“owner”: “data18000”,
“DDLs”: [
“ALTER TABLE scriptDraft.t_push ADD COLUMN studioIntersection TINYINT(1) NULL DEFAULT NULL COMMENT ‘是否工作室交集用户’ AFTER isWxPublic”
],
“synced”: [
“data18000”
],
“unsynced”: [
“data18001”,
“data18002”,
“data18003”,
“data18004”,
“data18005”,
“data18006”,
“data18007”
]
},
{
“ID”: “ai-scriptDraft.t_user_relevance”,
“task”: “ai”,
“mode”: “pessimistic”,
“owner”: “data18000”,
“DDLs”: [
“ALTER TABLE scriptDraft.t_user_relevance ADD COLUMN tags VARCHAR(255) NULL COMMENT ‘标签’ AFTER studioId”
],
“synced”: [
“data18000”
],
“unsynced”: [
“data18001”,
“data18002”,
“data18003”,
“data18004”,
“data18005”,
“data18006”,
“data18007”
]
},
{
“ID”: “ai-ai.t_user”,
“task”: “ai”,
“mode”: “pessimistic”,
“owner”: “data18002”,
“DDLs”: [
“ALTER TABLE ai.t_user ADD COLUMN config VARCHAR(128) CHARACTER SET UTF8MB4 COLLATE utf8mb4_unicode_ci NULL DEFAULT NULL COMMENT ‘用户配置’”
],
“synced”: [
“data18001”,
“data18002”,
“data18003”,
“data18005”,
“data18006”,
“data18007”
],
“unsynced”: [
“data18000”,
“data18004”
]
},
{
“ID”: “ai-aiimdata_0012.t_user”,
“task”: “ai”,
“mode”: “pessimistic”,
“owner”: “data18004”,
“DDLs”: [
“ALTER TABLE aiimdata_0012.t_user RENAME AS aiimdata_0012.t_user_1”
],
“synced”: [
“data18004”
],
“unsynced”: [
“data18000”,
“data18001”,
“data18002”,
“data18003”,
“data18005”,
“data18006”,
“data18007”
]
},
{
“ID”: “ai-scriptDraft.t_user”,
“task”: “ai”,
“mode”: “pessimistic”,
“owner”: “data18000”,
“DDLs”: [
“ALTER TABLE scriptDraft.t_user DISABLE KEYS”
],
“synced”: [
“data18000”
],
“unsynced”: [
“data18001”,
“data18002”,
“data18003”,
“data18004”,
“data18005”,
“data18006”,
“data18007”
]
}

$ tiup dmctl --master-addr 127.0.0.1:8261 shard-ddl-lock unlock ai-ai.t_user
-bash: ai: command not found
-bash: t_user: command not found
tiup is checking updates for component dmctl …
Starting component dmctl: /home/tidb/.tiup/components/dmctl/v6.6.0/dmctl/dmctl --master-addr 127.0.0.1:8261 shard-ddl-lock unlock ai-.
{
“result”: false,
“msg”: “can’t find task name from lock-ID”
}

$ tiup dmctl --master-addr 127.0.0.1:8261 shard-ddl-lock unlock ai-ai.t_user
tiup is checking updates for component dmctl …
Starting component dmctl: /home/tidb/.tiup/components/dmctl/v6.6.0/dmctl/dmctl --master-addr 127.0.0.1:8261 shard-ddl-lock unlock ai-ai.t_user
{
“result”: false,
“msg”: “can’t find task name from lock-ID”

6

dm 和 tidb 是否可以考虑使用同一个版本，要尽量使用同一个版本，否则很容易出现一些位置的问题~