运行Kafka准备就绪时出错。 org.apache.kafka.common.config.configexception:bootstrap.servers中没有可分解的bootstrap URL
我正在尝试在 3.1.0 Kafka 集群中部署 Schema-Registry,该集群具有 3 个运行良好的代理。我正在使用 Docker 20.10.11 和 Portainer 2.9.0。 我的问题是,其配置中的 boostrap.server 属性是错误的,因为它不断打印标题错误:
org.apache.kafka.common.config.ConfigException: No resolvable bootstrap urls given in bootstrap.servers
该属性的实际值是:
bootstrap.servers = [broker2:9092]
我的经纪人被命名为“kafka-brokerx”,是经纪人的编号。我如何更改该配置以便更正我的经纪人的名称?
我尝试将其放在 docker-compose 的环境部分中,但它不会改变它并继续打印错误。
- CONNECT_BOOTSTRAP_SERVERS= [kafka-broker1:9092, kafka-broker2:9092, kafka-broker3:9092]
我的码头工人组成:
version: "3.8"
networks:
net:
external: true
services:
kafka-broker1:
image: registry.gitlab.com/repo/kafka:2.13_3.1.0_v0.1
hostname: broker1
volumes:
- /var/volumes/kafka/config/server1.properties:/opt/kafka/config/server.properties
- /var/volumes/kafka/broker1-logs:/var/kafka-logs
environment:
- TZ=Europe/Madrid
networks:
- net
kafka-broker2:
image: registry.gitlab.com/repo/kafka:2.13_3.1.0_v0.1
hostname: broker2
volumes:
- /var/volumes/kafka/config/server2.properties:/opt/kafka/config/server.properties
- /var/volumes/kafka/broker2-logs:/var/kafka-logs
environment:
- TZ=Europe/Madrid
networks:
- net
kafka-broker3:
image: registry.gitlab.com/repo/kafka:2.13_3.1.0_v0.1
hostname: broker3
volumes:
- /var/volumes/kafka/config/server3.properties:/opt/kafka/config/server.properties
- /var/volumes/kafka/broker3-logs:/var/kafka-logs
environment:
- TZ=Europe/Madrid
networks:
- net
schema-registry:
image: confluentinc/cp-schema-registry:3.1.0
hostname: schema-registry
depends_on:
- broker
environment:
- SCHEMA_REGISTRY_HOST_NAME=schemaregistry
- SCHEMA_REGISTRY_KAFKASTORE_CONNECTION_URL= zookeeper_node
- CONNECT_BOOTSTRAP_SERVERS= [kafka-broker1:9092, kafka-broker2:9092, kafka-broker3:9092]
ports:
- 8081:8081
I am trying to deploy the Schema-Registry in a 3.1.0 Kafka cluster with 3 brokers that works well. I am using Docker 20.10.11 and Portainer 2.9.0.
My problem is that the boostrap.server attribute in its configuration is wrong as it keeps printing the error of the title:
org.apache.kafka.common.config.ConfigException: No resolvable bootstrap urls given in bootstrap.servers
The actual value of that property is:
bootstrap.servers = [broker2:9092]
My brokers are named "kafka-brokerx" being x the number of the broker. How can I change that configuration so that it takes to correct names for my broker??
I have tried putting this in the enviroment section of my docker-compose, but it doesn't change it and keeps printing the error.
- CONNECT_BOOTSTRAP_SERVERS= [kafka-broker1:9092, kafka-broker2:9092, kafka-broker3:9092]
My docker-compose:
version: "3.8"
networks:
net:
external: true
services:
kafka-broker1:
image: registry.gitlab.com/repo/kafka:2.13_3.1.0_v0.1
hostname: broker1
volumes:
- /var/volumes/kafka/config/server1.properties:/opt/kafka/config/server.properties
- /var/volumes/kafka/broker1-logs:/var/kafka-logs
environment:
- TZ=Europe/Madrid
networks:
- net
kafka-broker2:
image: registry.gitlab.com/repo/kafka:2.13_3.1.0_v0.1
hostname: broker2
volumes:
- /var/volumes/kafka/config/server2.properties:/opt/kafka/config/server.properties
- /var/volumes/kafka/broker2-logs:/var/kafka-logs
environment:
- TZ=Europe/Madrid
networks:
- net
kafka-broker3:
image: registry.gitlab.com/repo/kafka:2.13_3.1.0_v0.1
hostname: broker3
volumes:
- /var/volumes/kafka/config/server3.properties:/opt/kafka/config/server.properties
- /var/volumes/kafka/broker3-logs:/var/kafka-logs
environment:
- TZ=Europe/Madrid
networks:
- net
schema-registry:
image: confluentinc/cp-schema-registry:3.1.0
hostname: schema-registry
depends_on:
- broker
environment:
- SCHEMA_REGISTRY_HOST_NAME=schemaregistry
- SCHEMA_REGISTRY_KAFKASTORE_CONNECTION_URL= zookeeper_node
- CONNECT_BOOTSTRAP_SERVERS= [kafka-broker1:9092, kafka-broker2:9092, kafka-broker3:9092]
ports:
- 8081:8081
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
问题在于我忘了编写“网络”标签,因此经纪人和模式注册不在同一网络中,因此它不可能解决服务给出的DNS主机名。
The problem was that I forgot to write the "network" tag so the brokers and the schema-registry were not in the same network, so it was impossible for it to resolve de DNS hostnames given to the services.