[
https://issues.apache.org/jira/browse/KAFKA-3358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15239604#comment-15239604
]
Jason Gustafson commented on KAFKA-3358:
----------------------------------------
I can confirm Phil Luckhurst's investigation. This issue with the metadata
storm should go away automatically with the changes to the topic metadata
request, but it can also be fixed more simply with the following patch:
https://github.com/hachikuji/kafka/commit/428a973c36434f06282900209f1ea29a1343704e.
This change seems to make sense on its own, so perhaps it makes sense to merge
it in addition to the KIP-4 changes. Thoughts?
> Only request metadata updates once we have topics or a pattern subscription
> ---------------------------------------------------------------------------
>
> Key: KAFKA-3358
> URL: https://issues.apache.org/jira/browse/KAFKA-3358
> Project: Kafka
> Issue Type: Improvement
> Components: clients
> Affects Versions: 0.9.0.0, 0.9.0.1
> Reporter: Ismael Juma
> Assignee: Jason Gustafson
> Priority: Critical
> Fix For: 0.10.1.0
>
>
> The current code requests a metadata update for _all_ topics which can cause
> major load issues in large clusters.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
