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

Posted to dev@kafka.apache.org by "Manikumar (JIRA)" <ji...@apache.org> on 2017/10/30 12:24:00 UTC

[jira] [Resolved] (KAFKA-610) connect.timeout.ms seems to do the wrong thing in the producer

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

Manikumar resolved KAFKA-610.
-----------------------------
    Resolution: Auto Closed

Closing  inactive issue. The old producer is no longer supported.


> connect.timeout.ms seems to do the wrong thing in the producer
> --------------------------------------------------------------
>
>                 Key: KAFKA-610
>                 URL: https://issues.apache.org/jira/browse/KAFKA-610
>             Project: Kafka
>          Issue Type: Bug
>            Reporter: Jay Kreps
>
> This setting used to control the socket connection timeout. This is also what the documentation says:
> "the maximum time spent by kafka.producer.SyncProducer trying to connect to the kafka broker. Once it elapses, the producer throws an ERROR and stops."
> But it doesn't look to me that this parameter is being used at all. The only thing we do with it is check in a catch statement if that much time has ellapsed and then throw an error. Since we haven't set the connection timeout this is silly.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)