Gaurav created KAFKA-13402:
------------------------------
Summary: Kafka server does not handle SIGINT or stop command if
zookeeper abruptly closes/goes down
Key: KAFKA-13402
URL: https://issues.apache.org/jira/browse/KAFKA-13402
Project: Kafka
Issue Type: Bug
Affects Versions: 2.8.1, 2.8.0
Environment: OS: MacOS BigSur 11.6
Kafka - version 2.8.1, 2.8.0
Reporter: Gaurav
If zookeeper goes down abruptly and kafka server is trying to connect to
zookeeper, then pressing CTRL+C to stop kafka server does not work. Running
kafka-server-stop.sh also does not work. Kafka server just logs the SIGINT and
continues try connecting to zookeeper.
Steps:
# Run zookeeper and kafka server in local machine (single node)
# Press CTRL+C to stop Zookeeper. Observe that kafka server tries to connect
and logs error messages.
# Now, press CTRL+C to stop the Kafka server. Observe that it only logs the
SIGINT. Logs that it is terminating but does not terminate. Continues to retry
zookeeper connection
# Repeat step 3 but by running kafka-server-stop.sh command instead. Server
does not stop.
# Now bring up (start) the zookeeper and wait for Kafka server to successfully
connect to Zookeeper.
# Notice that, if kafka-server-stop has been run previously, it takes effect
only after the successful connections and kafka server stops as soon as it
connects to zookeeper.
# Notice that, if server-stop was not run, then pressing CTRL+C works just
fine after kafka server connects to zookeeper.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
