TiDB CDC Kafka

Translated
1

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

Original topic: tidb cdc kafka

| username: TiDBer_zZFAsV6w

[TiDB Usage Environment] Production Environment / Testing / PoC
[TiDB Version]
[Reproduction Path] What operations were performed when the issue occurred
[Encountered Issue: Issue Phenomenon and Impact]
[Resource Configuration] Go to TiDB Dashboard - Cluster Info - Hosts and take a screenshot of this page
[Attachments: Screenshots / Logs / Monitoring]

Error: [CDC:ErrKafkaNewProducer] new kafka producer: [CDC:ErrReachMaxTry] reach maximum try: 3, error: dial tcp: lookup node1 on 127.0.0.53:53: server misbehaving: dial tcp: lookup node1 on 127.0.0.53:53: server misbehaving

2
| username: TiDBer_zZFAsV6w | Original post link

Does anyone know what this means? Enable synchronization to Kafka.

3
| username: TiDBer_zZFAsV6w | Original post link

tiup cdc:v7.2.0 cli changefeed create --server=http://192.168.3.4:8300 --sink-uri=“kafka://192.168.3.177:9092,192.168.3.188:9092,192.168.3.199:9092,192.168.3.201:9092,192.168.3.211:9092/ticdc?protocol=canal-json&kafka-version=3.3.1&partition-num=3&replication-factor=1&max-message-bytes=1048576” --changefeed-id=“tidb-ods-task” --config /home/ac/changefeed_config.toml

4
| username: Jellybean | Original post link

Is the status of the downstream Kafka node normal?
The error seems to be caused by a retry limit being exceeded when trying to connect to the downstream while creating the Kafka consumer.

5
| username: Fly-bird | Original post link

What is node1?

6
| username: FutureDB | Original post link

It looks like there is an exception connecting to Kafka. You can check whether Kafka and the connection to Kafka are normal.

7
| username: Kongdom | Original post link

Server Misbehaving is a type of server failure, which means the server cannot perform the expected tasks as anticipated. For example, it may not successfully respond to requests, meet the expected response time, or complete tasks within the normal maintenance window, among other factors.

8
| username: dba远航 | Original post link

Check if the node 127.0.0.53:53 is functioning properly.

9
| username: TiDBer_zZFAsV6w | Original post link

It is already working. Kafka configuration listener endpoint is set with host, listener, and advertised.listeners using the custom host node1. Caching the IP solved the issue.

10
| username: Kongdom | Original post link

:+1: :+1: :+1: Remember to mark the best answer so that more people can quickly get the solution.

11
| username: linnana | Original post link

The problem has been solved.

12
| username: system | Original post link

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