You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Bill Bejeck (Jira)" <ji...@apache.org> on 2020/08/20 16:06:00 UTC

[jira] [Updated] (KAFKA-9893) Configurable TCP connection timeout and improve the initial metadata fetch

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

Bill Bejeck updated KAFKA-9893:
-------------------------------
    Fix Version/s: 2.7.0

> Configurable TCP connection timeout and improve the initial metadata fetch
> --------------------------------------------------------------------------
>
>                 Key: KAFKA-9893
>                 URL: https://issues.apache.org/jira/browse/KAFKA-9893
>             Project: Kafka
>          Issue Type: New Feature
>    Affects Versions: 2.7.0
>            Reporter: Cheng Tan
>            Assignee: Cheng Tan
>            Priority: Major
>             Fix For: 2.7.0
>
>
> This issue has two parts:
>  # Support transportation layer connection timeout described in KIP-601
>  # Optimize the logic for NetworkClient.leastLoadedNode()
> Changes:
>  # Added a new common client configuration parameter socket.connection.setup.timeout.ms to the NetworkClient. Handle potential transportation layer timeout using the same approach as it handling potential request timeout.
>  # When no connected channel exists, leastLoadedNode() will now provide a disconnected node that has the least number of failed attempts. 
>  # ClusterConnectionStates will keep the connecting node ids. Now it also has several new public methods to provide per connection relavant data.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)