You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2019/05/07 20:14:00 UTC

[jira] [Commented] (KAFKA-8275) NetworkClient leastLoadedNode selection should consider throttled nodes

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

ASF GitHub Bot commented on KAFKA-8275:
---------------------------------------

hachikuji commented on pull request #6619: KAFKA-8275; Take throttling into account when choosing least loaded node
URL: https://github.com/apache/kafka/pull/6619
 
 
   
 
----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> NetworkClient leastLoadedNode selection should consider throttled nodes
> -----------------------------------------------------------------------
>
>                 Key: KAFKA-8275
>                 URL: https://issues.apache.org/jira/browse/KAFKA-8275
>             Project: Kafka
>          Issue Type: Bug
>            Reporter: Jason Gustafson
>            Assignee: Jason Gustafson
>            Priority: Major
>
> The leastLoadedNode() function is intended to find any available node. It is smart in the sense that it considers the number of inflight requests and reconnect backoff, but it has not been updated to take into account client throttling. If we have an available node which is not throttled, we should use it.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)