[
https://issues.apache.org/jira/browse/KAFKA-3760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15303140#comment-15303140
]
ASF GitHub Bot commented on KAFKA-3760:
---------------------------------------
GitHub user theduderog opened a pull request:
https://github.com/apache/kafka/pull/1436
KAFKA-3760: Set broker state as running after publishing to ZooKeeper
Redoing PR #1426 with a JIRA
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/theduderog/kafka broker-running-after-zk
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/1436.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1436
----
commit 54052cb17b1572b50ce770168a30c5d9cbcb278a
Author: Roger Hoover <roger.hoo...@gmail.com>
Date: 2016-05-25T01:37:24Z
Setting broker state as running after publishing to ZK
commit cc8ce55f874121dc4c26a63ffd6c8c7eb3a8107d
Author: Roger Hoover <roger.hoo...@gmail.com>
Date: 2016-05-25T01:40:51Z
Restore imports
----
> 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: Jun Rao
> Priority: Minor
>
> 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)
