You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Jay Kreps (JIRA)" <ji...@apache.org> on 2012/10/04 05:19:07 UTC
[jira] [Updated] (KAFKA-543) Metadata request from
DefaultEventHandler.handle repeats same topic over and over
[ https://issues.apache.org/jira/browse/KAFKA-543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jay Kreps updated KAFKA-543:
----------------------------
Summary: Metadata request from DefaultEventHandler.handle repeats same topic over and over (was: Something is wrong with the metadata request in DefaultEventHandler.handle)
> Metadata request from DefaultEventHandler.handle repeats same topic over and over
> ---------------------------------------------------------------------------------
>
> Key: KAFKA-543
> URL: https://issues.apache.org/jira/browse/KAFKA-543
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 0.8
> Reporter: Jay Kreps
>
> It looks like we are calling BrokerPartitionInfo.updateInfo() with a list of the same topic repeated many times:
> Here is the line:
> Utils.swallowError(brokerPartitionInfo.updateInfo(outstandingProduceRequests.map(_.getTopic)))
> The outstandingProduceRequests can (and generally would) have many entries for the same topic.
> For example if I use the producer performance test with the default batch size on a topic "test" my metadata request will have the topic "test" repeated 200 times. On the server side we do several zk reads for each of these repetitions.
> This is causing the metadata api to timeout in my perf test periodically.
> I think the fix is simply to de-duplicate prior to the call (and perhaps again on the server in case of a misbehaving client).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira