[
https://issues.apache.org/jira/browse/KAFKA-4631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15890223#comment-15890223
]
ASF GitHub Bot commented on KAFKA-4631:
---------------------------------------
GitHub user rajinisivaram opened a pull request:
https://github.com/apache/kafka/pull/2622
KAFKA-4631: Request metadata in consumer if topic/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.
Metadata refresh is also requested if a subscribe topic or assigned partition
doesn't exist.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/rajinisivaram/kafka KAFKA-4631
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/2622.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 #2622
----
commit 406427953b2789e5a717136bac6b0b3ada5eb9eb
Author: Rajini Sivaram <rajinisiva...@googlemail.com>
Date: 2017-02-28T12:09:44Z
KAFKA-4631: Request metadata in consumer if topic/partitions unavailable
----
> Refresh consumer metadata more frequently for unknown subscribed topics
> -----------------------------------------------------------------------
>
> Key: KAFKA-4631
> URL: https://issues.apache.org/jira/browse/KAFKA-4631
> Project: Kafka
> Issue Type: Bug
> Components: consumer
> Reporter: Jason Gustafson
> Assignee: Matthias J. Sax
> Priority: Minor
> Fix For: 0.10.3.0
>
>
> By default, the consumer refreshes metadata every 5 minutes. In testing, it
> can often happen that a topic is created at about the same time that the
> consumer is started. In the worst case, creation finishes after the consumer
> fetches metadata, and the test must wait 5 minutes for the consumer to
> refresh metadata in order to discover the topic. To address this problem,
> users can decrease the metadata refresh interval, but this means more
> frequent refreshes even after all topics are known. An improvement would be
> to internally let the consumer fetch metadata more frequently when the
> consumer encounters unknown topics. Perhaps every 5-10 seconds would be
> reasonable, for example.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
