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

Posted to jira@kafka.apache.org by "goalfull (via GitHub)" <gi...@apache.org> on 2024/06/13 13:13:13 UTC

Re: [PR] KAFKA-8275; Take throttling into account when choosing least loaded node [kafka]

goalfull commented on PR #6619:
URL: https://github.com/apache/kafka/pull/6619#issuecomment-2165634721

   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. What do you think?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: jira-unsubscribe@kafka.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org