[KAFKA-14887] ZK session timeout can cause broker to shutdown

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.7.0, 2.8.0, 2.7.1, 3.1.0, 2.7.2, 2.8.1, 3.0.0, 3.0.1, 2.8.2, 3.2.0, 3.1.1, 3.3.0, 3.0.2, 3.1.2, 3.2.1, 3.4.0, 3.2.2, 3.2.3, 3.3.1, 3.3.2
• Fix Version/s: 2.7.3, 3.2.4, 3.1.3, 3.0.3, 3.5.0, 3.4.1, 3.3.3, 2.8.3
• Assignee: Ron Dagostino
• Reporter: Ron Dagostino
• Created: 10/Apr/23 20:51
• Updated: 21/Apr/23 01:11
• Resolved: 21/Apr/23 00:13

Description

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.

Issue Links

• duplicates: KAFKA-14890 Kafka initiates shutdown due to connectivity problem with Zookeeper and FatalExitError from ChangeNotificationProcessorThread
• links to: GitHub Pull Request #13532