[KAFKA-9893] Configurable TCP connection timeout and improve the initial metadata fetch

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Implemented
• Affects Version/s: 2.7.0
• Fix Version/s: 2.7.0
• Component/s: core
• Assignee: Cheng Tan
• Reporter: Cheng Tan
• Created: 20/Apr/20 21:20
• Updated: 26/Aug/20 14:42
• Resolved: 01/Jul/20 22:08

Description

This issue has two parts:

1. Support transportation layer connection timeout described in KIP-601
2. Optimize the logic for NetworkClient.leastLoadedNode()

Changes:

1. 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.
2. When no connected channel exists, leastLoadedNode() will now provide a disconnected node that has the least number of failed attempts. 
3. ClusterConnectionStates will keep the connecting node ids. Now it also has several new public methods to provide per connection relavant data.

Issue Links

• links to: GitHub Pull Request #8544
• links to: GitHub Pull Request #8683
• mentioned in: Page Loading...
• mentioned in: Page Loading...