After upgrading to 6.5.3, CDC cannot synchronize data to downstream

Translated
1

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

Original topic: 升级6.5.3后cdc无法向下游同步数据

| username: xmlianfeng

[TiDB Usage Environment] Production Environment
[TiDB Version] v6.5.3
[Reproduction Path] Upgraded from 6.1.5 to 6.5.3
[Encountered Problem]
After the upgrade, the CDC synchronization to downstream Kafka tasks got stuck. There are about 150 tasks and around 1300 tables being synchronized. I checked the Sink write rows and there are none… How should I troubleshoot this?

cdc-log.txt (5.6 MB)

image
image1296×483 82.1 KB

image
image1288×162 9.58 KB

2
| username: redgame | Original post link

The log contains unsupported data types or type conversion issues, which may be caused by data format incompatibility or programming errors.

3
| username: LingJin | Original post link

“unsupported type comes from logging when an object has a callback that zap cannot recognize, which should not be related to the stalling issue.”

4
| username: nongfushanquan | Original post link

Has it recovered now? I see a lot of [CDC:ErrPDBatchLoadRegions] pd batch load regions failed: receive Regions with no peer: messages in the logs. It looks like there was an error in the region information returned from PD.

5
| username: Anna | Original post link

Take a look at this: 上游tidb 读写量很大的时候，ticdc任务卡住了，必须重启才能恢复 - #14，来自 lxzkenney - TiDB 的问答社区

6
| username: system | Original post link

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