tidb dm incremental实时同步数据报错

[jaybing926 (gongshubing)]

先用dm full全量同步，记录全量同步返回的binlog file and pos，用dm incremental做实时增量备份，报如下错误~~ ，求大佬帮忙看下~，谢谢~

» query-status
{
“result”: true,
“msg”: “”,
“tasks”: [
{
“taskName”: “task29”,
“taskStatus”: “Finished”,
“sources”: [
“mysql-29”
]
},
{
“taskName”: “task29-incr”,
“taskStatus”: “Error - Some error occurred in subtask. Please run query-status task29-incr to get more details.”,
“sources”: [
“mysql-29”
]
}
]
}
» query-status task29-incr
{
“result”: true,
“msg”: “”,
“sources”: [
{
“result”: true,
“msg”: “”,
“sourceStatus”: {
“source”: “mysql-29”,
“worker”: “dm-192.168.241.60-8262”,
“result”: null,
“relayStatus”: null
},
“subTaskStatus”: [
{
“name”: “task29-incr”,
“stage”: “Paused”,
“unit”: “Sync”,
“result”: {
“isCanceled”: false,
“errors”: [
{
“ErrCode”: 36014,
“ErrClass”: “sync-unit”,
“ErrScope”: “internal”,
“ErrLevel”: “high”,
“Message”: “startLocation: [position: (mysql-bin.000002, 855440924), gtid-set: ], endLocation: [position: (mysql-bin.000002, 855441117), gtid-set: ], origin SQL: [UPDATE xpost SET author_id = ‘7722186023’ WHERE xpost.url = ‘Sina Visitor System’]: query UPDATE xpost SET author_id = ‘7722186023’ WHERE xpost.url = ‘Sina Visitor System’: only support ROW format binlog, unexpected DML statement found in query event”,
“RawCause”: “”,
“Workaround”: “”
}
],
“detail”: null
},
“unresolvedDDLLockID”: “”,
“sync”: {
“totalEvents”: “6568”,
“totalTps”: “0”,
“recentTps”: “0”,
“masterBinlog”: “(mysql-bin.000002, 977164165)”,
“masterBinlogGtid”: “”,
“syncerBinlog”: “(mysql-bin.000002, 855440833)”,
“syncerBinlogGtid”: “”,
“blockingDDLs”: [
],
“unresolvedGroups”: [
],
“synced”: false,
“binlogType”: “remote”,
“secondsBehindMaster”: “0”,
“blockDDLOwner”: “”,
“conflictMsg”: “”
}
}
]
}
]
}

[h5n1]

@jaybing926

only support ROW format binlog, unexpected DML statement found in query event”,

上游binlog格式是啥？binlog_format

[边城元元]

only support ROW format binlog, unexpected DML statement found in query event”,

看看binglog的类型

[jaybing926 (gongshubing)]

ROW，不是ROW那么应该通不过check的吧

[jaybing926 (gongshubing)]

binlog_format是 row了呀，要不是row的话 check task都会报错的，
好像是我开始的binlog file post是有问题的，跟我指定的pos对不上呢

[jaybing926 (gongshubing)]

mysql-instances:

上游实例或者复制组 ID。

source-id: “mysql-29”
meta:
binlog-name: “mysql-bin.000003”
binlog-pos: 4399957

我的yaml文件里指定的这个 binlog file pos，是从这个位置开始读吗？ 日志的报错杂是这个Pos之前的呢，file也不对

[Hacker007]

only support ROW format binlog, unexpected DML statement found in query event”, 提示很明显呀

[jaybing926 (gongshubing)]

主要问题是他不啥没按照我配置的 binlog file and pos 同步数据，
我配置的是：
binlog-name: “mysql-bin.000003”
binlog-pos: 4399957
但错误是：mysql-bin.000002 这个file是有非row格式的日志的，这是正常的

[db_user]

当前的同步位置是这，明显是000002文件啊，你可以去dm_meta库看下对应任务表的binlog，pos,另外看下上游这两个配置
show variables like ‘%binlog_format%’;
show variables like ‘%binlog_row_image%’;