无法解析 'kafka:9092':名称解析暂时失败

时间:2021-06-01 17:53:28

标签: c# docker apache-kafka docker-compose

我遇到了一些问题

<块引用>

%3|1622567567.487|失败|rdkafka#consumer-2| [thrd:GroupCoordinator]: GroupCoordinator: kafka:9092: Failed to resolve 'kafka:9092': 名称解析暂时失败(在状态 CONNECT 27431ms 后,1 个相同的错误被抑制)

如何解决这个问题,知道吗? 屏幕截图中描述的问题

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"
                };

enter image description here

enter image description here

动物园管理员日志 enter image description here

enter image description here

2 个答案:

答案 0 :(得分:0)

在您的图像中,代理因无法解析 zookeeper:2181 而死亡。因此,您的应用将无法解析 kafka:9092,因为代理未运行。

您应该运行 docker-compose logs zookeeper 以验证它是否正常启动。

答案 1 :(得分:0)

当我使用 docker stats 时,我注意到 ms server 占用了大量内存。这是我问题的根源