You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by yaojuncn <gi...@git.apache.org> on 2016/11/06 05:15:25 UTC

[GitHub] kafka pull request #2107: KAFKA-4385-avoid-unnecessary-meta-request-overhead

GitHub user yaojuncn opened a pull request:

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

    KAFKA-4385-avoid-unnecessary-meta-request-overhead

    add a producer config: "metadata.fetch.max.count"
    default to Integer.MAX_VALUE, then everything is the same as before;
    when specified, the metadata request will be limited by both "metadata.fetch.timeout.ms" (time limit) and "metadata.fetch.max.count" (request count)
    
    when "auto.create.topics.enable=false", "metadata.fetch.max.count" can be set as 1, so that it could avoid lots of unncessary duplicate metadata

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

    $ git pull https://github.com/yaojuncn/kafka KAFKA-4385-avoid-unnecessary-meta-request-overhead

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

    https://github.com/apache/kafka/pull/2107.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 #2107
    
----
commit 20311836762f02a29b880b7edee76567b1d60c7c
Author: yaojuncn <ya...@users.noreply.github.com>
Date:   2016-11-06T05:12:22Z

    KAFKA-4385-avoid-unnecessary-meta-request-overhead
    
    add a producer config: "metadata.fetch.max.count"
    default to Integer.MAX_VALUE, then everything is the same as before;
    when specified, the metadata request will be limited by both "metadata.fetch.timeout.ms" (time limit) and "metadata.fetch.max.count" (request count)
    
    when "auto.create.topics.enable=false", "metadata.fetch.max.count" can be set as 1, so that it could avoid lots of unncessary duplicate metadata

----


---
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.
---