CDC Synchronization Error to Kafka

Translated
1

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

Original topic: cdc同步数据到kafka报错

| username: 像风一样的男子

[TiDB Usage Environment] Production
[TiDB Version] 5.4.3
[Encountered Issue]
There are occasional errors when CDC synchronizes data to Kafka. The error screenshot is as follows:

image
image1566×676 28.7 KB

After a while, the CDC status becomes FATAL.
How should I handle this to resolve the error?

2
| username: xfworld | Original post link

Check the status of the region. This error indicates that the region data cannot be covered…

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

Can you specifically explain how to handle it?

4
| username: songxuecheng | Original post link

Check if there are any replicas in an abnormal state.

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

My database is single-replica.

6
| username: xfworld | Original post link

Production with a single replica? At least three replicas are needed… :scream:

7
| username: Meditator | Original post link

For regions like this, confirm the status information to see if there are any anomalies?

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

A replica, used for backups.

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

It looks normal.

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

After upgrading to version 6.1, I found that Kafka shuts down abnormally. How should I solve this?

image
image1866×528 35.9 KB

11
| username: Lucien-卢西恩 | Original post link

Are there similar issues with other downstream targets? Why is the upstream TiDB using a single replica solution? This is not recommended. Have you checked what the error logs in Kafka are? Can you provide them?

12
| username: system | Original post link

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