kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pengwei (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-4862) Kafka client connect to a shutdown node will block for a long time
Date Sat, 23 Sep 2017 05:22:00 GMT

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

Pengwei commented on KAFKA-4862:
--------------------------------

[~guozhang] This jira is for the KIP-148, I think I can merge it into the 1.0.0 if this KIP
is voted, thanks

> Kafka client connect to a shutdown node will block for a long time
> ------------------------------------------------------------------
>
>                 Key: KAFKA-4862
>                 URL: https://issues.apache.org/jira/browse/KAFKA-4862
>             Project: Kafka
>          Issue Type: Bug
>    Affects Versions: 0.9.0.0, 0.10.2.0
>            Reporter: Pengwei
>            Assignee: Pengwei
>             Fix For: 1.0.0
>
>
> Currently in our test env, we found after one of the broker node crash(reboot or os crash),
the client maybe still connecting to the crash node to send metadata request or other request,
and it need about several  minutes to aware the connection is timeout then try another node
to connect to send the request.  Then the client may still not aware the metadata change after
several minutes.
> We don't have a connection timeout for the network client, we should add a connection
timeout for the client



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

Mime
View raw message