You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ignite.apache.org by "david (Jira)" <ji...@apache.org> on 2020/06/01 07:29:00 UTC

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

david created IGNITE-13099:
------------------------------

             Summary: .net thin client - node selection on start up incorrect - wrong node chosen in ClientFailoverSocket GetNextSocket
                 Key: IGNITE-13099
                 URL: https://issues.apache.org/jira/browse/IGNITE-13099
             Project: Ignite
          Issue Type: Bug
          Components: thin client
    Affects Versions: 2.8.1, 2.8
         Environment: .net core 3.1 / windows server 2019 / c#
            Reporter: david


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

 



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