Ignite Client is taking a long time to connect with large number of Client connections

[kotamrajuyashasvi <ko...@gmail.com>]

Hi

I setup 4 Ignite Servers on 4 different machines. Then Ignite Clients are
started on other machine to connect to these Ignite servers. A single Client
is getting connected fast. But as the number of Client connections increase
the connection time is decreasing. Is there any way to speed up the
connection speed.
The connection speed is also random. Sometimes all Clients get connected
quickly and sometimes they don't.

I have already seen the post: 
http://apache-ignite-users.70518.x6.nabble.com/Client-Connection-to-Ignite-takes-time-td4739.html

But I was wondering if we can anyhow speed up the Ignite Clients connection
speed without using same Ignite Client Instance and using multi-threaded
Java Clients. Are there any limitations on number of Clients 
that can be connected to the Ignite cluster as such or any other
configuration options.



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

Re: Ignite Client is taking a long time to connect with large number of Client connections

["ilya.kasnacheev" <il...@gmail.com>]

Hello!

Ignite Clients are called "Thick", and indeed, they are pretty heavy-weight.
They are full functional nodes, and as such, they have to join topology when
starting and properly leave topology when stopping. This is long process. It
also has to wait for any pending transactions in cluster, that's where you
are seeing unpredictable times.

Ignite Clients are fully thread safe. You should never need to have more
than one client per long-running process. You should avoid having Ignite
Clients in short-lived processes. Reuse Ignite Clients where possible.

You can use JDBC Thin client, ODBC client or REST API (for simple use cases)
to avoid said limitations. There's currently work underway to introduce more
thin clients for various platforms.
https://apacheignite-sql.readme.io/docs/jdbc-driver
https://apacheignite.readme.io/docs/rest-api and other platforms &
protocols.

There's no hard limit on number of clients, but practically I would not
recommend having more than a few dozens, and definitely not having clients
come and go all the time.

Regards,



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