[
https://issues.apache.org/jira/browse/KAFKA-16996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17870840#comment-17870840
]
Chia-Ping Tsai commented on KAFKA-16996:
----------------------------------------
[~goalfull] thanks for your reporter. I will take a look later. We are running
the release recently, so the community is a bit busy :)
> The leastLoadedNode() function in kafka-client may choose a faulty node
> during the consumer thread starting and meanwhile one of the KAFKA server
> node is dead.
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: KAFKA-16996
> URL: https://issues.apache.org/jira/browse/KAFKA-16996
> Project: Kafka
> Issue Type: Bug
> Components: clients
> Affects Versions: 2.0.1, 2.3.0, 3.6.0
> Reporter: Goufu
> Priority: Blocker
>
> The leastLoadedNode() function has a bug during the consumer process starting
> period. The function sendMetadataRequest() called by
> getTopicMetadataRequest() uses a random node which maybe faulty since every
> node‘s state recorded in the client thread is not ready yet. It happened in
> my production environment during my consumer thread restarting and meanwhile
> one of the KAFKA server node is dead. Then the client startup failed.
> I'm using the kafka-client-2.0.1.jar. I have checked the source code of
> higher versions and the issue still exists.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
