[GitHub] kafka pull request: Setting broker state as running after publishi...

[asfgit]

Github user asfgit closed the pull request at:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] kafka pull request: Setting broker state as running after publishi...

[theduderog]

GitHub user theduderog opened a pull request:

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

Setting broker state as running after publishing to ZK

@junrao 

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.



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/1426.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 #1426


commit 54052cb17b1572b50ce770168a30c5d9cbcb278a
Author: Roger Hoover 
Date:   2016-05-25T01:37:24Z

Setting broker state as running after publishing to ZK

commit cc8ce55f874121dc4c26a63ffd6c8c7eb3a8107d
Author: Roger Hoover 
Date:   2016-05-25T01:40:51Z

Restore imports




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---