v6.5.2
发现ticdc同步任务失败
{
“id”: “kunta2bigdata”,
“namespace”: “default”,
“summary”: {
“state”: “failed”,
“tso”: 441737524319092736,
“checkpoint”: “2023-05-26 17:55:26.144”,
“error”: {
“addr”: “192.168.86.93:8300”,
“code”: “CDC:ErrGCTTLExceeded”,
“message”: “[CDC:ErrGCTTLExceeded]the checkpoint-ts(441737524319092736) lag of the changefeed({default kunta2bigdata}) has exceeded the GC TTL”
}
}
},
删除任务重新创建任务,失败
tiup cdc cli changefeed create --disable-gc-check --server=http://XXXXX:8300 --sink-uri=“mysql://XXXXX:XXXXX@tidb-XXXXX:4000?safe-mode=true” --changefeed-id=“XXXXX2bigdata” --start-ts=441737524319092736 --config=cdc.yaml
tiup is checking updates for component cdc …
Starting component cdc
: /home/admin/.tiup/components/cdc/v6.5.2/cdc cli changefeed create --disable-gc-check --server=http://ticdc-XXXXX:8300 --sink-uri=mysql://repl:XXXXX@tidb-XXXXX:4000?safe-mode=true --changefeed-id=kunta2bigdata --start-ts=441737524319092736 --config=cdc.yaml
Replicate lag (65h39m57.4s) is larger than 1 days, large data may cause OOM, confirm to continue at your own risk [Y/N]
Y
Error: [CDC:ErrMetaListDatabases]meta store list databases: [tikv:9006]GC life time is shorter than transaction duration, transaction starts at 2023-05-26 17:55:26.144 +0800 CST, GC safe point is 2023-05-29 11:25:16.295 +0800 CST
Replicate lag (65h39m57.4s) is larger than 1 days, large data may cause OOM, confirm to continue at your own risk [Y/N]
Y
Error: [CDC:ErrMetaListDatabases]meta store list databases:
[tikv:9006]GC life time is shorter than transaction duration,
transaction starts at 2023-05-26 17:55:26.144 +0800 CST,
GC safe point is 2023-05-29 11:25:16.295 +0800 CST
这错误描述得很清楚咯
你的场景是什么呢?诉求是什么?
感觉模版白给你设了… 还是要在问一遍…
诉求就是从失败的时间点重新同步数据到下游
binlog 解析出来。 手工入库到最近时间,然后指定一个 最近的时间点看看。
估计得从头来了
gc时间不够了,你出问题时间点的gc都已经被清理了,只能重新同步了
感觉得加监控告警了,这都相差好几天了,遇到问题及时修复,避免GC 周期结束,已经没有相关数据