CDC Task Error After Adding Remote Node to Downstream Kafka

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

Original topic: 下游kafka添加异地节点后,cdc任务报错

| username: l940399478

[TiDB Usage Environment] Production Environment
[TiDB Version] 6.5.2
When migrating to a remote location by adding or removing nodes in downstream Kafka, after adding the remote node, the CDC task starts reporting an error:
“code”: “CDC:ErrKafkaNewSaramaProducer”,
“message”: “[CDC:ErrKafkaNewSaramaProducer]new sarama producer: read tcp CDC node IP:14692-> remote Kafka node IP:9092: i/o timeout”
When the remote Kafka node is removed, the CDC task returns to normal.

| username: 小龙虾爱大龙虾 | Original post link

Isn’t the network disconnected and timed out?

| username: l940399478 | Original post link

The network test is successful.

| username: 小龙虾爱大龙虾 | Original post link

Have all the CDC nodes been tested?

| username: wangccsy | Original post link

Check if the network is smooth. TimeOut usually means it cannot connect.

| username: l940399478 | Original post link

All tests have been done, and the network is fine. I see that the CDC logs list all the topics. We have quite a few topics in this Kafka setup. Could this be causing the timeout?

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

Didn’t you post about this issue last time? It’s still not resolved?

| username: l940399478 | Original post link

No, after the last time, I tried to modify the parameters in the CDC task: auto-create-topic to false, as well as dial-timeout, write-timeout, and read-timeout. None of them worked.

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

Your requirement is strange. Who would have Kafka nodes across data centers?

| username: l940399478 | Original post link

We are relocating our data center, and the strategy for Kafka migration is by adding and removing nodes.

| username: dba远航 | Original post link

Check the network status, connection configuration, and permissions.