You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@kafka.apache.org by "jaikiran (JIRA)" <ji...@apache.org> on 2015/01/05 08:04:34 UTC

[jira] [Updated] (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:all-tabpanel ]

jaikiran updated KAFKA-1836:
----------------------------
    Status: Patch Available  (was: Open)

I've attached a patch which handles <= 0 values in the awaitUpdate method. I've also added a testcase to verify this change. Can you take a look at this and see if this makes sense?


> 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)