[
https://issues.apache.org/jira/browse/KAFKA-6128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16220385#comment-16220385
]
Alastair Munro commented on KAFKA-6128:
---------------------------------------
We seem to have a broken zookeeper. If I test on another setup, we are good. So
in summary kafka is connecting to a load balanced zookeeper:2181 cluster, and
zookeeper.connect uses this. When a node is stopped, the id
/brokers/ids/<broker-id> is not removed from some of the zookeeper nodes. On
restart the broker connects to one of the zookeeper nodes where
/brokers/ids/<broker-id> has not been updated and reports the issue of not
being shutdown properly.
> Shutdown script does not do a clean shutdown
> --------------------------------------------
>
> Key: KAFKA-6128
> URL: https://issues.apache.org/jira/browse/KAFKA-6128
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 0.11.0.1
> Reporter: Alastair Munro
> Priority: Minor
>
> Shutdown script (sending term signal) does not do a clean shutdown.
> We are running kafka in kubernetes/openshift 0.11.0.0. The statefulset kafka
> runs the shutdown script prior to stopping the pod kafka is running on:
> {code}
> lifecycle:
> preStop:
> exec:
> command:
> - ./bin/kafka-server-stop.sh
> {code}
> This worked perfectly in 0.11.0.0 but doesn't in 0.11.0.1. Also we see the
> same behaviour if we send a TERM signal to the kafka process (same as the
> shutdown script).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
