[
https://issues.apache.org/jira/browse/KAFKA-4862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15971112#comment-15971112
]
ASF GitHub Bot commented on KAFKA-4862:
---------------------------------------
GitHub user pengwei-li opened a pull request:
https://github.com/apache/kafka/pull/2861
KAFKA-4862: Kafka client connect to a shutdown node will block for a long
time
Author: pengwei <pengwei...@huawei.com>
Reviewers: Jiangjie Qin <becket....@gmail.com>
@becketqin
Modify: Add a connect timeout for the kafka client to avoid long blocking if
network is down
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/pengwei-li/kafka trunk
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/2861.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2861
----
commit a920d4e9807add634cc44e4b7cf9e156edd515cf
Author: pengwei-li <pengwei...@huawei.com>
Date: 2016-07-10T00:31:56Z
KAFKA-1429: Yet another deadlock in controller shutdown
Author: pengwei <pengwei...@huawei.com>
Reviewers: NA
commit 2a5a4322c8ac359587f05b459588cd2b5843a2ac
Author: pengwei-li <pengwei...@huawei.com>
Date: 2016-11-20T11:31:21Z
Merge branch 'trunk' of https://github.com/apache/kafka into trunk
commit b827a8b4f249050ca40db9f14e8e10b01650a6b8
Author: pengwei-li <pengwei...@huawei.com>
Date: 2016-11-20T12:18:49Z
Merge branch 'trunk' of https://github.com/apache/kafka into trunk
commit 43e186f223dee1e24177a87ee6888eaae91547d9
Author: pengwei-li <pengwei...@huawei.com>
Date: 2016-11-27T01:54:00Z
Merge branch 'trunk' of https://github.com/apache/kafka into trunk
commit febe4f433452a2ad8849a329bc5c9f4d1507a317
Author: pengwei-li <pengwei...@huawei.com>
Date: 2016-11-27T03:31:26Z
issue:KAFKA-4229
reason: controoler can't start afeter several zk expired event
commit f6791b29998a49dffbefdf5414584b7849bfbd3c
Author: c00353482 <c00353...@huaweiobz.com>
Date: 2017-01-04T02:25:55Z
Merge branch 'trunk' of https://github.com/apache/kafka into trunk
commit 2e7090567aa4cd2ffe02fa927bcfdd062029087b
Author: c00353482 <c00353...@huaweiobz.com>
Date: 2017-04-01T07:58:09Z
Merge https://github.com/apache/kafka into trunk
commit fb77b2e7a32d1a678b45aa035211597793ff1fd0
Author: c00353482 <c00353...@huaweiobz.com>
Date: 2017-04-14T08:16:04Z
Merge branch 'trunk' of https://github.com/apache/kafka into trunk
commit 270e0b45c08893463c8bf4f553d5a506d6603d41
Author: c00353482 <c00353...@huaweiobz.com>
Date: 2017-04-17T08:08:35Z
Merge branch 'trunk' of https://github.com/apache/kafka into trunk
commit 13c6134dfb2313f946e37d86985ef8b4336706ed
Author: c00353482 <c00353...@huaweiobz.com>
Date: 2017-04-17T14:15:52Z
KAFKA-4862: Kafka client connect to a shutdown node will block for a long
time
Add a connect time out for the kafka client to avoid long blocking if
network is down
Author: pengwei <pengwei...@huawei.com>
Reviewers: Ismael Juma <ism...@juma.me.uk>
----
> 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: 0.11.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.3.15#6346)
