[IGNITE-13099] .net thin client - node selection on start up incorrect - wrong node chosen in ClientFailoverSocket GetNextSocket

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.8, 2.8.1
• Component/s: thin client

Environment

.net core 3.1 / windows server 2019 / c#

• Ignite Flags: Docs Required, Release Notes Required
• Assignee: Unassigned
• Reporter: david
• Reviewer: Ilya Kasnacheev
• Created: 01/Jun/20 07:28
• Updated: 01/Jun/20 07:28

Description

To reproduce 
var cfg = new IgniteClientConfiguration()
{
Endpoints = new List<string>()

{ "localhost","ignite01","ignite02","ignite03","ignite04" }

};
Ignition.StartClient(cfg)

Log show ignite Thin client connecting to "ignite01" and not "localhost" first - the first elment in the array?

if Port randes are used: eg: 

Endpoints = new List<string>()

{ "localhost:10800..10810","ignite01:10800..10810","ignite02:10800..10810" //snip }

};
logs show connecting to localhost:10801 and localhost:10800 is skipped