kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Grant Henke (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (KAFKA-3691) Confusing logging during metadata update timeout
Date Wed, 15 Jun 2016 15:21:09 GMT

     [ https://issues.apache.org/jira/browse/KAFKA-3691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Grant Henke updated KAFKA-3691:
    Fix Version/s:

> 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:
>            Reporter: Grant Henke
>            Assignee: Grant Henke
>             Fix For:,
> 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

View raw message