TiCDC connection to Kafka error persists after upgrade

Translated
1

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

Original topic: ticdc链接kafka报错,升级后报错依然存在

| username: TiDBer_DVnkdzKV

To improve efficiency, please provide the following information. A clear problem description can help resolve the issue faster:
【TiDB Usage Environment】Production
【TiDB Version】tidb 6.2 cdc v6.2.0
【Encountered Problem】ticdc connection to Kafka error
【Reproduction Path】tiup cdc cli changefeed create --sink-uri=‘kafka://172.21.0.9:9092/test?kafka-version=2.6.0&partition-num=1&max-message-bytes=67108864&replication-factor=1&protocol=canal-json’ --changefeed-id=“replication-task-2” --server=http://172.21.0.9:8300
【Problem Phenomenon and Impact】
Error: [CDC:ErrKafkaNewSaramaProducer]new sarama producer: dial tcp: lookup VM-0-9-centos on 183.60.83.19:53: no such host

2
| username: TiDBer_DVnkdzKV | Original post link

The reason has been found: the Kafka version was passed incorrectly.

3
| username: system | Original post link

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