You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by rajinisivaram <gi...@git.apache.org> on 2017/02/28 13:15:18 UTC

[GitHub] kafka pull request #2608: KAFKA-4779: Request metadata in consumer if partit...

GitHub user rajinisivaram opened a pull request:

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

    KAFKA-4779: Request metadata in consumer if partitions unavailable

    If leader node of one more more partitions in a consumer subscription are temporarily unavailable, request metadata refresh so that partitions skipped for assignment dont have to wait for metadata expiry before reassignment.

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

    $ git pull https://github.com/rajinisivaram/kafka KAFKA-4779-consumer-metadata

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

    https://github.com/apache/kafka/pull/2608.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 #2608
    
----
commit af5ef2b98314653de5ae098e8c45eb84b81685e7
Author: Rajini Sivaram <ra...@googlemail.com>
Date:   2017-02-28T12:09:44Z

    KAFKA-4779: Request metadata in consumer if partitions unavailable

----


---
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 #2608: KAFKA-4779: Request metadata in consumer if partit...

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

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


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