TiCDC synchronizes data, checkpoint_time does not advance

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

Original topic: TiCDC同步数据,checkpoit_time没有往前推进

| username: 泰迪比爱好者

[TiDB Usage Environment] Production Environment / Testing / Poc
[TiDB Version] V7.1.1
[Reproduction Path] What operations were performed when the issue occurred
[Encountered Issue: Issue Phenomenon and Impact]
[Resource Configuration]
[Attachments: Screenshots / Logs / Monitoring]
When I used TiCDC to synchronize data from one TiDB cluster to another TiDB cluster, I found that the checkpoint_time did not advance and was lagging by several days. The logs reported the following error.


Has anyone encountered a similar situation?

| username: xfworld | Original post link

Check the region ID in the logs to see if it actually exists.

Based on the logs, there are some issues in the cluster that prevent CDC from properly retrieving data to make progress…

| username: 像风一样的男子 | Original post link

Check if the region ID with the error in pd ctl is normal.

| username: dba远航 | Original post link

The above shows leader switch failure.

| username: Fly-bird | Original post link

I’ve encountered this problem before. Your dcd command is incorrect; try it again with the full path.

| username: 泰迪比爱好者 | Original post link

It appeared after running for a period of time.

| username: 泰迪比爱好者 | Original post link

How do you see it? I’m new to TiDB and not quite sure how to operate it.

| username: 泰迪比爱好者 | Original post link

I feel that it is caused by large-scale updates and deletions of data upstream.

| username: TiDBer_小阿飞 | Original post link

Check if this region is normal.

| username: 泰迪比爱好者 | Original post link

Where did you see it?

| username: TiDBer_小阿飞 | Original post link

SHOW TABLE [table_name] REGIONS [WhereClauseOptional];

| username: 泰迪比爱好者 | Original post link

I don’t know which table it is.

| username: 泰迪比爱好者 | Original post link

The latest screenshot is as follows

| username: TiDBer_小阿飞 | Original post link

| username: 像风一样的男子 | Original post link

Then you need to take a good look at the documentation

| username: 泰迪比爱好者 | Original post link

It looks normal.

| username: 泰迪比爱好者 | Original post link

It looks normal.

| username: xfworld | Original post link

Check and see… Which table does it belong to?


Then also locate whether this table has undergone large transaction processing, or what operations were performed before and after…

| username: 泰迪比爱好者 | Original post link

This table has undergone large-scale updates and deletions of data.

| username: xfworld | Original post link

Try following the instructions in the documentation: TiCDC 常见问题解答 | PingCAP 文档中心

Check the configuration first…