[
https://issues.apache.org/jira/browse/KAFKA-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16252192#comment-16252192
]
Prasanna Gautam commented on KAFKA-5473:
----------------------------------------
[~junrao] [~ijuma] I have updated the PR without the config. I don't quite
follow what you mean by adding in kafkaController.newSession() because I can't
find it in KafkaController anymore. I'm currently running the startup function
if the state callback stops returning SessionEstablishmentError and if it's not
already in a startingUp state. Did you mean a different way to run it?
Also, I have been getting ducktape errors on TravisCI for the tests. I'd assume
this requires some ducktape tests too?
> 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.1.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)
