[
https://issues.apache.org/jira/browse/KAFKA-3691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-3691:
-------------------------------
Resolution: Fixed
Fix Version/s: (was: 0.10.0.1)
Status: Resolved (was: Patch Available)
Issue resolved by pull request 1509
[https://github.com/apache/kafka/pull/1509]
> Confusing logging during metadata update timeout
> ------------------------------------------------
>
> Key: KAFKA-3691
> URL: https://issues.apache.org/jira/browse/KAFKA-3691
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 0.10.0.0
> Reporter: Grant Henke
> Assignee: Grant Henke
> Fix For: 0.10.1.0
>
>
> When the KafkaProducer calls waitOnMetadata it will loop decrementing the
> remainingWaitMs until it either receives the request metadata or runs out of
> time. Inside the loop Metadata.awaitUpdate is called with the value in
> remainingWaitMs. Inside Metadata.awaitUpdate a timeout execption could be
> thrown using the remainingWaitMs which results in messages like:
> {noformat}
> org.apache.kafka.common.errors.TimeoutException: Failed to update metadata
> after 3 ms.
> {noformat}
> Perhaps we should catch the exception and log the real maxWaitMs or change
> the language to make the exception more clear.
> Note: I still need to investigate further to be sure exactly when this
> happens, but wanted to log the jira to make sure this is not forgotten.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
