[ https://issues.apache.org/jira/browse/KAFKA-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16184653#comment-16184653 ]
Prasanna Gautam commented on KAFKA-5473: ---------------------------------------- Think I can make it to the code freeze. I'm at a conference this week and it's a bit of hassle to get the env well setup on the machine I have here. Is there an easy way to bootstrap the environment for testing? I'd like to reuse anything that's already been done for that. > 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)