[KAFKA-5473] handle ZK session expiration properly when a new session can't be established

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.9.0.0
• Fix Version/s: 1.1.0
• Assignee: Prasanna Gautam
• Reporter: Jun Rao
• Reviewer: Ismael Juma
• Created: 19/Jun/17 21:19
• Updated: 07/May/18 14:35
• Resolved: 15/Dec/17 22:48

Description

In https://issues.apache.org/jira/browse/KAFKA-2405, we change the logic in handling ZK session expiration a bit. If a new ZK session can't be established after session expiration, we just log an error and continue. However, this can leave the broker in a bad state since it's up, but not registered from the controller's perspective. Replicas on this broker may never to be in sync.

Issue Links

• duplicates: KAFKA-3984 Broker doesn't retry reconnecting to an expired Zookeeper connection
• is duplicated by: KAFKA-4041 kafka unable to reconnect to zookeeper behind an ELB
• is duplicated by: KAFKA-2864 Bad zookeeper host causes broker to shutdown uncleanly and stall producers
• is duplicated by: KAFKA-2193 Intermittent network + DNS issues can cause brokers to permanently drop out of a cluster
• is related to: KAFKA-4871 Kafka doesn't respect TTL on Zookeeper hostname - crash if zookeeper IP changes
• links to: GitHub Pull Request #3990