[IGNITE-14220] Shuffle server addresses for thin clients

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.9.1
• Component/s: thin client
• Ignite Flags: Docs Required, Release Notes Required
• Assignee: Unassigned
• Reporter: Stephen Darlington
• Created: 22/Feb/21 18:17
• Updated: 22/Feb/21 18:17

Description

To connect to a grid from a thin-client, we provide a list of servers and ports. If partition awareness is disabled, Ignite connects to the first node.

In the case where there are lots of thin clients, they all end up connecting to the same server node.

This is improved somewhat when partition awareness is enabled. JCache requests go directly to the data node in question. But SQL queries will all be sent to the same node (since the algorithm is deterministic).

If the list were "shuffled" before use, the load would end up balanced across the cluster.