Failed to resolve 'kafka:9092': Temporary failure in name resolution

Question

I faced with some issue

%3|1622567567.487|FAIL|rdkafka#consumer-2| [thrd:GroupCoordinator]: GroupCoordinator: kafka:9092: Failed to resolve 'kafka:9092': Temporary failure in name resolution (after 27431ms in state CONNECT, 1 identical error(s) suppressed)

How to resolve that issue, any idea? The issue describes in the screenshot

nkafka-console-app:
    build: 
      context: dotNet/examples/
      dockerfile: Src/KafkaConsoleApp/Dockerfile
    environment:
      - producer_topic=console_topic_test
      - consumer_topic=console_topic_test
      - kafka_endpoint=kafka:9092
    depends_on:
      - kafka   
 zookeeper:
    image: confluentinc/cp-zookeeper:5.2.1
    restart: always
    environment:
     ZOOKEEPER_SERVER_ID: 1
     ZOOKEEPER_CLIENT_PORT: "2181"
     ZOOKEEPER_TICK_TIME: "2000"
    ports:
      - "2181:2181"

kafka:
    image: confluentinc/cp-enterprise-kafka:5.2.1
    depends_on:
      - zookeeper
    ports:
      - "29092:29092"
    environment:
      KAFKA_ZOOKEEPER_CONNECT: "zookeeper:2181"
      KAFKA_LISTENER_SECURITY_PROTOCOL_MAP: PLAINTEXT:PLAINTEXT,PLAINTEXT_HOST:PLAINTEXT
      KAFKA_INTER_BROKER_LISTENER_NAME: PLAINTEXT
      KAFKA_ADVERTISED_LISTENERS: PLAINTEXT://kafka:9092,PLAINTEXT_HOST://localhost:29092
      KAFKA_OFFSETS_TOPIC_REPLICATION_FACTOR: 1

var config = new ProducerConfig { BootstrapServers = conf.kafka_endpoint, BatchSize = 100000, LingerMs = 100 };

var configConsumer = new ConsumerConfig
                {
                    BootstrapServers = kafkaEndpoint,
                    EnableAutoOffsetStore = false,
                    EnableAutoCommit = true,
                    AutoCommitIntervalMs = 10000,
                    AutoOffsetReset = AutoOffsetReset.Earliest,
                    GroupId = "group.id"
                };

Zookeeper logs

I don't see a console app container in your docker-compose file? — MaartenDev, Jun 01 '21 at 18:09
if you are running your app on Windows and trying to connect to Kafka running in the container you need to add "kafka" to your hosts file. Otherwise, you can use ` localhost:9092` as a hostname — OlegI, Jun 01 '21 at 20:16

score 0 · Answer 1 · answered Jun 01 '21 at 20:09

0

In your image, the broker died because it couldn't resolve zookeeper:2181. Therefore, your app will fail to resolve kafka:9092 because the broker isn't running .

You should run docker-compose logs zookeeper to verify that it started okay.

answered Jun 01 '21 at 20:09

OneCricketeer

179,855
19
132
245

okay, but why zookeeper died? What configuration I have to add ? – Valera Fedorenko Jun 01 '21 at 20:11
Also, `depends_on` doesn't ensure the services actually start _successfully_, only that the containers start in-order. I generally suggest running `docker-compose up -d zookeeper kafka` then wait a minute before starting your own app – OneCricketeer Jun 01 '21 at 20:14
I have just added logs, look plz screenshot – Valera Fedorenko Jun 01 '21 at 20:18
I just tried to get new logs but now docker-compose logs zookeeper not responding. Docker crashed – Valera Fedorenko Jun 01 '21 at 20:22
Seems to be working, although, there are a lot of exceptions – OneCricketeer Jun 01 '21 at 20:26
1

I assume you're on Windows? You need to increase the Docker memory to at least 4GB – OneCricketeer Jun 01 '21 at 20:26
I defined Memory: 5.00 GB – Valera Fedorenko Jun 01 '21 at 20:27

score -1 · Answer 2 · answered Jun 02 '21 at 11:47

-1

When I used docker stats I notice that ms server takes a lot of memory. It was the root of my issue

answered Jun 02 '21 at 11:47

Valera Fedorenko

99
1
9

Failed to resolve 'kafka:9092': Temporary failure in name resolution

2 Answers2