Mauraza
commented
2 years ago Hi @florian-besser,
Could you add BITNAMI_DEBUG=true to your docker-compose to see if there is more information?
version: "3.7"
services:
zookeeper:
container_name: zookeeper
networks:
- mynet
image: bitnami/zookeeper:3.7.1
ports:
- 2181:2181
environment:
- ALLOW_ANONYMOUS_LOGIN=yes
- BITNAMI_DEBUG=true
restart: always
deploy:
resources:
limits:
memory: 256M
kafka:
container_name: kafka
networks:
- mynet
depends_on:
- "zookeeper"
image: bitnami/kafka:2.8.1
ports:
- 9092:9092
environment:
- ALLOW_PLAINTEXT_LISTENER=yes
- KAFKA_BROKER_ID=500
- KAFKA_CFG_BROKER_ID_GENERATION_ENABLE=false
- KAFKA_CFG_ZOOKEEPER_CONNECT=zookeeper:2181
- KAFKA_LISTENERS=PLAINTEXT://:9092,DOCKER://:29092
- KAFKA_ADVERTISED_LISTENERS=PLAINTEXT://localhost:9092,DOCKER://kafka:29092
- KAFKA_LISTENER_SECURITY_PROTOCOL_MAP=PLAINTEXT:PLAINTEXT,DOCKER:PLAINTEXT
- KAFKA_HEAP_OPTS=-Xmx512m -Xms512m
- BITNAMI_DEBUG=true
restart: always
deploy:
resources:
limits:
memory: 512M
networks:
mynet:
name: mynet
florian-besser
github-actions[bot]
carrodher
Name and Version
bitnami/zookeeper:3.7.1
What steps will reproduce the bug?
Use the following
docker-composefile:Most of the time both apps come up and work perfectly fine.
Sometimes Zookeeper refuses connections (see below)
What is the expected behavior?
Both apps should come up all the time; or the container should self-detect it is unhealthy and restart until it is healthy.
What do you see instead?
Kafka produces the following log and then ends in a restart spiral:
Please note the
ZooKeeperClientTimeoutExceptiontowards the end of the log.At the same time Zookeeper does not seem to log any errors:
I would like to see some WARN / ERROR lines in ZK.
To debug whether the issue was in Kafka or in ZK I did the following:
So it seems ZK somehow is unable to receive traffic.
Additional information
After a simple
docker restart zookeeperthings start working again.