Hello!

 

Thin clients don’t change topology version, you may think of it

as a different API for performing cluster operations alongside with

REST API, WebConsole and others.[1]

 

When you call Ignition.StartClient,  your application establishes a new TCP connection

to a server node using default 10800 port and utilizes it for performing cluster operations.

 

On the other side, calling Ignition.Start will start a new node instance.

The process of starting a new NODE is much complicated than opening a single TCP connection.

It involves the Discovery API – a new node needs to find others in order to form a cluster

(47500 port), as well as the Communication SPI – nodes, should send messages to

each other (47100 port). That’s true, a node could be either a client or a server [2],

but you should distinguish a regular client node that forms a topology and

a thin client connection that doesn’t.

 

[1] - https://apacheignite-net.readme.io/docs/thin-client

[2] - https://apacheignite.readme.io/docs/clients-vs-servers

 

 

From: SidP
Sent: Thursday, December 26, 2019 1:35 PM
To: [email protected]
Subject: Re: C# client not able to connect to cluster using IP address

 

Hi,

 

Do you mean i should try this?

 

Keep Server config as it is,

In TcpDiscoverySpi node keep value as

 

<value>MyHostName:47500..47504</value>

 

C# thin Client tries to connect with below code

 

private static IgniteClientConfiguration GetIgniteClientConfiguration()

        {

            return new IgniteClientConfiguration

            {

                Host = "MyHostName",

                SocketTimeout = TimeSpan.FromSeconds(15)

            };

       }

 

* IgniteThinClient = Ignition.StartClient(GetIgniteClientConfiguration());*

 

Code pass through above line without any exception, but in server log,

Topology snapshot as below

Topology snapshot [ver=1, locNode=f19c8896, servers=1, *clients=0*,

state=ACTIVE, CPUs=8, offheap=3.2GB, heap=1.0GB]

 

Please let me know if i am doing anything wrong?

 

Also in case, if ignite server config has some different ports specified for

example (46000..46505) then how thin client should connect to one of the

node by specified one of the port from this (46000..46505) range, right?

 

 

 

 

 

--

Sent from: http://apache-ignite-users.70518.x6.nabble.com/

 

Reply via email to