Denis Washington created KAFKA-13680:
----------------------------------------
Summary: Kafka Streams application remains in RUNNING state
although all stream threads shut down
Key: KAFKA-13680
URL: https://issues.apache.org/jira/browse/KAFKA-13680
Project: Kafka
Issue Type: Bug
Components: streams
Affects Versions: 3.0.0
Reporter: Denis Washington
We have a Kafka Streams application that is configured with
{{LogAndFailExceptionHandler}} as deserialization error handler. In the Kafka
Streams version we used previously (2.7), a deserialization error that causes
all stream threads to shut down would ultimately move the application to the
ERROR state.
However, after updating to Kafka Streams 3.0.0, we see a different behavior:
the stream threads still shut down, but the Kafka Streams application stays in
the RUNNING state. It thus gets into a "zombie" state not detected by our
monitoring.
It may be worth noting that this application has global state stores, and that
the global stream thread was not affected by the deserialization error where we
noticed the problem.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
