[ https://issues.apache.org/jira/browse/KAFKA-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16184683#comment-16184683 ]
Ismael Juma commented on KAFKA-5473: ------------------------------------ We would need the PR to be submitted ASAP so that there's time for review though. If your availability is restricted, would you be OK with someone else picking it up? This can cause some very bad behaviour, so I'm eager to get it fixed for 1.0.0. > handle ZK session expiration properly when a new session can't be established > ----------------------------------------------------------------------------- > > Key: KAFKA-5473 > URL: https://issues.apache.org/jira/browse/KAFKA-5473 > Project: Kafka > Issue Type: Sub-task > Affects Versions: 0.9.0.0 > Reporter: Jun Rao > Assignee: Prasanna Gautam > Fix For: 1.0.0 > > > 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. -- This message was sent by Atlassian JIRA (v6.4.14#64029)