[jira] [Commented] (KAFKA-3638) Using kafka-console-producer with invalid broker list weirds to unexpected behavior

["Grant Henke (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KAFKA-3638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15263182#comment-15263182 ] 

Grant Henke commented on KAFKA-3638:
------------------------------------

[~jarcec] This looks like it might be covered by KAFKA-3468 and KAFKA-2998.

> Using kafka-console-producer with invalid broker list weirds to unexpected behavior
> -----------------------------------------------------------------------------------
>
>                 Key: KAFKA-3638
>                 URL: https://issues.apache.org/jira/browse/KAFKA-3638
>             Project: Kafka
>          Issue Type: Bug
>            Reporter: Jarek Jarcec Cecho
>
> I've messed the port when running console producer on my test cluster and instead of {{ConnectionRefused}} exception or something like that, I didn't get any immediate error. After I tried to produce some messages I got nothing and after a minute or so got {{ERROR}} about updating metadata:
> {code}
> [root@centos6 ~]# kafka-console-producer --broker-list localhost:666 --topic source
> asfasdf
> [2016-04-28 14:28:01,950] ERROR Error when sending message to topic source with key: null, value: 7 bytes with error: Failed to update metadata after 60000 ms. (org.apache.kafka.clients.producer.internals.ErrorLoggingCallback)
> {code}
> Would it perhaps make sense to throw more accurate exception in this case?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)