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 2014/12/29 23:17:13 UTC
[jira] [Commented] (KAFKA-1836) metadata.fetch.timeout.ms set to
zero blocks forever
[ https://issues.apache.org/jira/browse/KAFKA-1836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14260483#comment-14260483 ]
Jay Kreps commented on KAFKA-1836:
----------------------------------
Looks like Metadata.awaitUpdate() always calls Object.wait(maxWaitMs) even if maxWaitMs is 0. Unfortunately Object.wait(0) doesn't mean wait for zero ms, it means wait forever. So it should be an easy fix--we need an if statement here to check for a wait time of 0.
> metadata.fetch.timeout.ms set to zero blocks forever
> ----------------------------------------------------
>
> Key: KAFKA-1836
> URL: https://issues.apache.org/jira/browse/KAFKA-1836
> Project: Kafka
> Issue Type: Bug
> Components: clients
> Affects Versions: 0.8.2
> Reporter: Paul Pearcy
> Priority: Minor
> Labels: newbie
>
> You can easily work around this by setting the timeout value to 1ms, but 0ms should mean 0ms or at least have the behavior documented.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)