[ https://issues.apache.org/jira/browse/KAFKA-9189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17304909#comment-17304909 ]
Ismael Juma commented on KAFKA-9189: ------------------------------------ Discussed with [~david.mao] offline and he said he would not have time to do this soon, so we agreed I could pick it up. > Shutdown is blocked if connection to Zookeeper is lost > ------------------------------------------------------ > > Key: KAFKA-9189 > URL: https://issues.apache.org/jira/browse/KAFKA-9189 > Project: Kafka > Issue Type: Bug > Components: core > Affects Versions: 2.3.0 > Environment: Linux, Docker 19.03.4 > Reporter: Boris Granveaud > Assignee: David Mao > Priority: Minor > > We are using Kafka and Zookeeper in Docker swarm stacks. When we undeploy a > stack, sometimes Kafka doesn't shutdown properly and is finally killed by > Docker (thus leaving potentially corrupted files). > Here are the steps to reproduce (simple Docker, no swarm): > > {code:java} > docker network create test > docker run -d --network test --name zk --rm zookeeper:3.5.6 > docker run --network test --name kf --rm -e "KAFKA_ZOOKEEPER_CONNECT=zk:2181" > -e "KAFKA_ADVERTISED_LISTENERS=INSIDE://:9091" -e > "KAFKA_LISTENER_SECURITY_PROTOCOL_MAP=INSIDE:PLAINTEXT" -e > "KAFKA_INTER_BROKER_LISTENER_NAME=INSIDE" confluentinc/cp-kafka:5.3.1 > {code} > > In another shell: > > {code:java} > docker stop zk > docker stop kf > {code} > -- This message was sent by Atlassian Jira (v8.3.4#803005)