kafka.zookeeper.ZooKeeperClientTimeoutException: Timed out waiting for connection while in state: CONNECTING
docker-compose启动kafka连接zookeeper异常原配置文件最终配置文件
docker-compose启动kafka连接zookeeper异常
原配置文件
version: '3.0'
services:
zookepper:
image: zookeeper:1.0 # 原镜像`wurstmeister/zookeeper
restart: always
privileged: true
container_name: zookeeper # 容器名为'zookeeper'
environment:
SET_CONTAINER_TIMEZONE: "true"
CONTAINER_TIMEZONE: "Asia/Shanghai"
ports: # 映射端口
- "2181:2181"
kafka:
image: kafka:1.0 # 原镜像`wurstmeister/kafka`
container_name: kafka # 容器名为'kafka'
restart: always
privileged: true
environment:
SET_CONTAINER_TIMEZONE: "true"
CONTAINER_TIMEZONE: "Asia/Shanghai" # 设置环境变量,相当于docker run命>令中的-e
KAFKA_BROKER_ID: 0 # 在kafka集群中,每个kafka都有一个BROKER_ID来区分自己
KAFKA_ADVERTISED_LISTENERS: PLAINTEXT://192.168.1.17:9092 # TODO 将kafka的地址端口注册给zookeeper
KAFKA_LISTENERS: PLAINTEXT://0.0.0.0:9092 # 配置kafka的监听端口
KAFKA_ZOOKEEPER_CONNECT: 192.168.1.17:2181
KAFKA_CREATE_TOPICS: "file_manager"
KAFKA_HEAP_OPTS: -Xmx1G -Xms256M
ports: # 映射端口
- "9092:9092"
depends_on: # 解决容器依赖启动先后问题
- zookepper
之前使用该文件从来没有问题,换了一套网络环境之后,启动之后查看kafka日志报错kafka.zookeeper.ZooKeeperClientTimeoutException。个人感觉还是网络的原因。所以将docker网络默认的桥接模式改为host模式,最终解决问题
最终配置文件
version: '3.0'
services:
zookepper:
image: zookeeper:1.0 # 原镜像`wurstmeister/zookeeper
restart: always
privileged: true
container_name: zookeeper # 容器名为'zookeeper'
network_mode: host
environment:
SET_CONTAINER_TIMEZONE: "true"
CONTAINER_TIMEZONE: "Asia/Shanghai"
ZOOKEEPER_CLIENT_PORT: 2181
kafka:
image: kafka:1.0 # 原镜像`wurstmeister/kafka`
container_name: kafka # 容器名为'kafka'
restart: always
privileged: true
network_mode: host
environment:
SET_CONTAINER_TIMEZONE: "true"
CONTAINER_TIMEZONE: "Asia/Shanghai" # 设置环境变量,相当于docker run命>令中的-e
KAFKA_BROKER_ID: 0 # 在kafka集群中,每个kafka都有一个BROKER_ID来区分自己
KAFKA_ADVERTISED_LISTENERS: PLAINTEXT://192.168.1.17:9092 # TODO 将kafka的地址端口注册给zookeeper
KAFKA_LISTENERS: PLAINTEXT://0.0.0.0:9092 # 配置kafka的监听端口
KAFKA_ZOOKEEPER_CONNECT: 192.168.1.17:2181
KAFKA_CREATE_TOPICS: "file_manager"
KAFKA_HEAP_OPTS: -Xmx1G -Xms256M
depends_on: # 解决容器依赖启动先后问题
- zookepper
推荐阅读
发表评论