You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@kafka.apache.org by "Jun Rao (JIRA)" <ji...@apache.org> on 2017/06/19 21:20:00 UTC

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

Jun Rao created KAFKA-5473:
------------------------------

             Summary: 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


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)