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

Posted to dev@kafka.apache.org by "Jason Gustafson (JIRA)" <ji...@apache.org> on 2019/05/07 20:14:00 UTC

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

     [ https://issues.apache.org/jira/browse/KAFKA-8275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Gustafson resolved KAFKA-8275.
------------------------------------
       Resolution: Fixed
    Fix Version/s: 2.3.0

> 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
>             Fix For: 2.3.0
>
>
> 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)