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

Posted to dev@kafka.apache.org by "Ismael Juma (JIRA)" <ji...@apache.org> on 2016/05/26 23:44:12 UTC

[jira] [Resolved] (KAFKA-3760) Set broker state as running after publishing to ZooKeeper

     [ https://issues.apache.org/jira/browse/KAFKA-3760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ismael Juma resolved KAFKA-3760.
--------------------------------
       Resolution: Fixed
         Assignee: Roger Hoover  (was: Jun Rao)
         Reviewer: Jun Rao
    Fix Version/s: 0.10.1.0

Fixed via https://github.com/apache/kafka/pull/1426.

> Set broker state as running after publishing to ZooKeeper
> ---------------------------------------------------------
>
>                 Key: KAFKA-3760
>                 URL: https://issues.apache.org/jira/browse/KAFKA-3760
>             Project: Kafka
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 0.10.0.0
>            Reporter: Roger Hoover
>            Assignee: Roger Hoover
>            Priority: Minor
>             Fix For: 0.10.1.0
>
>
> Currently, the broker state is set to running before it registers itself in ZooKeeper. This is too early in the broker lifecycle. If clients use the broker state as an indicator that the broker is ready to accept requests, they will get errors. This change is to delay setting the broker state to running until it's registered in ZK.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)