Dru Panchal commented on KAFKA-1733:

As seen in the following file: The fix was made for the 0.9.0 release and it 
was also back-ported into 0.8.2

Also, as seen in the following file: The last release where this issue still 
exists is: 0.8.1

> Producer.send will block indeterminately when broker is unavailable.
> --------------------------------------------------------------------
>                 Key: KAFKA-1733
>                 URL: https://issues.apache.org/jira/browse/KAFKA-1733
>             Project: Kafka
>          Issue Type: Bug
>          Components: core, producer 
>    Affects Versions:
>            Reporter: Marc Chung
>            Assignee: Marc Chung
>             Fix For:,
>         Attachments: kafka-1733-add-connectTimeoutMs.patch
> This is a follow up to the conversation here:
> https://mail-archives.apache.org/mod_mbox/kafka-dev/201409.mbox/%3ccaog_4qymoejhkbo0n31+a-ujx0z5unsisd5wbrmn-xtx7gi...@mail.gmail.com%3E
> During ClientUtils.fetchTopicMetadata, if the broker is unavailable, 
> socket.connect will block indeterminately. Any retry policy 
> (message.send.max.retries) further increases the time spent waiting for the 
> socket to connect.
> The root fix is to add a connection timeout value to the BlockingChannel's 
> socket configuration, like so:
> {noformat}
> -channel.socket.connect(new InetSocketAddress(host, port))
> +channel.socket.connect(new InetSocketAddress(host, port), connectTimeoutMs)
> {noformat}
> The simplest thing to do here would be to have a constant, default value that 
> would be applied to every socket configuration. 
> Is that acceptable? 

This message was sent by Atlassian JIRA

Reply via email to