You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by granthenke <gi...@git.apache.org> on 2016/04/30 07:53:19 UTC

[GitHub] kafka pull request: MINOR: MetadataCache brokerId is not set on fi...

GitHub user granthenke opened a pull request:

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

    MINOR: MetadataCache brokerId is not set on first run with generated …

    …broker id
    
    This is because the id passed into the MetadataCache is the value from the config before the real broker id is generated.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/granthenke/kafka metadata-id

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/kafka/pull/1299.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 #1299
    
----
commit b9df1caea4e14b9d4f7c0b445f841c0e4b4309c0
Author: Grant Henke <gr...@gmail.com>
Date:   2016-04-30T05:51:29Z

    MINOR: MetadataCache brokerId is not set on first run with generated broker id
    
    This is because the id passed into the MetadataCache is the value from the config before the real broker id is generated.

----


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] kafka pull request: MINOR: MetadataCache brokerId is not set on fi...

Posted by granthenke <gi...@git.apache.org>.
Github user granthenke closed the pull request at:

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


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---