[
https://issues.apache.org/jira/browse/KAFKA-4631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Gustafson updated KAFKA-4631:
-----------------------------------
Description: 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. (was: 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, it finishes after the consumer
fetches metadata, and the test must wait 5 minutes for the consumer to refresh
metadata. 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.)
> 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
> Reporter: Jason Gustafson
> Assignee: Matthias J. Sax
> Fix For: 0.10.2.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.4#6332)
