[jira] [Assigned] (KAFKA-14887) ZK session timeout can cause broker to shutdown

["Ron Dagostino (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/KAFKA-14887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ron Dagostino reassigned KAFKA-14887:
-------------------------------------

    Assignee: Ron Dagostino

> ZK session timeout can cause broker to shutdown
> -----------------------------------------------
>
>                 Key: KAFKA-14887
>                 URL: https://issues.apache.org/jira/browse/KAFKA-14887
>             Project: Kafka
>          Issue Type: Improvement
>    Affects Versions: 3.3.2, 3.3.1, 3.2.3, 3.2.2, 3.4.0, 3.2.1, 3.1.2, 3.0.2, 3.3.0, 3.1.1, 3.2.0, 2.8.2, 3.0.1, 3.0.0, 2.8.1, 2.7.2, 3.1.0, 2.7.1, 2.8.0, 2.7.0
>            Reporter: Ron Dagostino
>            Assignee: Ron Dagostino
>            Priority: Major
>
> We have the following code in FinalizedFeatureChangeListener.scala which will exit regardless of the type of exception that is thrown when trying to process feature changes:
>         case e: Exception => {
>           error("Failed to process feature ZK node change event. The broker will eventually exit.", e)
>           throw new FatalExitError(1)
> The issue here is that this does not distinguish between exceptions caused by an inability to process a feature change and an exception caused by a ZooKeeper session timeout.  We want to shut the broker down for the former case, but we do NOT want to shut the broker down in the latter case; the ZooKeeper session will eventually be reestablished, and we can continue processing at that time.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)