[
https://issues.apache.org/jira/browse/KAFKA-4862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guozhang Wang updated KAFKA-4862:
---------------------------------
*Reminder to the contributor / reviewer of the PR*: please note that the code
deadline for 1.0.0 is less than 2 weeks away (Oct. 4th). Please re-evaluate
your JIRA and see if it still makes sense to be merged into 1.0.0 or it could
be pushed out to 1.1.0, or be closed directly if the JIRA itself is not valid
any more, or re-assign yourself as contributor / committer if you are no longer
working on the JIRA.
> 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)
