[IGNITE-18637] Java thin client: Connections balancing

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.15
• Component/s: thin client
• Labels: important ise
• Release Note: Java thin client: Added connections balancing (use random open connection for requests instead of default)
• Ignite Flags: Docs Required, Release Notes Required
• Assignee: Aleksey Plekhanov
• Reporter: Aleksey Plekhanov
• Created: 25/Jan/23 13:39
• Updated: 26/Apr/23 18:27
• Resolved: 26/Jan/23 11:37

Description

Since Ignite 2.12 java thin client always connects to the first address from the provided address list. In typical configuration this leads to overloading an one server node and underloading other server nodes. 

To improve workload distribution we can:

1. Choose random first channel from the range of addresses with the same (minimal) port.
2. If partition awareness is enabled use random open channel instead of default channel for operations which can't be mapped to a certain node. 

Issue Links

• is caused by: IGNITE-15807 In case of port is absent in IgniteClient first of all try connect on default port
• links to: GitHub Pull Request #10497