Re: Reconnect is not allowed due to applied throttling

2020-08-04 Thread Alex Plehanov
Hello,

Ignite thin client applies connection throttling if you have several
failed attempts to connect to some server (this server will be skipped for
some time to avoid waiting for connection timeouts on each attempt to
connect, the client will try to connect to the next servers if they are
configured).
By default, if your server is unavailable and you have 3 in a row
ClientConnectionException during 30 seconds on the same channel throttling
will be applied. The next real attempt to connect to this server will be
made after 30 seconds from the time of the first exception.
Connection throttling parameters can be changed by ClientConfiguration (see
reconnectThrottlingPeriod and reconnectThrottlingRetries).


вт, 4 авг. 2020 г. в 13:37, AravindJP :

> Hi ,
> I am getting below exception after running an Ignite client running
> continuously for 48 hrs . My client is running on java (spring boot) . I am
> using singleton  instance of IgniteClient object to connect and persist
> data.
>
> Ignite version 2.8.0
>
> 020-08-04 10:02:18.520 ERROR 1 --- [sub-subscriber3]: Exception with
> org.
> apache.ignite.client.ClientConnectionException: Reconnect is not allowed
> due
> to applied throttling
> at
>
> org.apache.ignite.internal.client.thin.ReliableChannel$ClientChannelHolder.getOrCreateChannel(ReliableCha
> nnel.java:448)
> at
>
> org.apache.ignite.internal.client.thin.ReliableChannel$ClientChannelHolder.getOrCreateChannel(ReliableCha
> nnel.java:439)
> at
>
> org.apache.ignite.internal.client.thin.ReliableChannel$ClientChannelHolder.access$100(ReliableChannel.jav
> a:395)
> at
>
> org.apache.ignite.internal.client.thin.ReliableChannel.channel(ReliableChannel.java:318)
> at
>
> org.apache.ignite.internal.client.thin.ReliableChannel.service(ReliableChannel.java:158)
> at
>
> org.apache.ignite.internal.client.thin.ReliableChannel.request(ReliableChannel.java:187)
> at
>
> org.apache.ignite.internal.client.thin.TcpClientCache.putAll(TcpClientCache.java:210)
> a
>
>
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>


Re: Reconnect is not allowed due to applied throttling

2020-08-04 Thread akurbanov
Hello,

This was implemented as a part of
https://issues.apache.org/jira/browse/IGNITE-11898.

Please check the javadocs for the ClientConfiguration class: 
https://github.com/apache/ignite/commit/d72a123e122ffe1b4f715f98c2db5d79293f0c90
https://github.com/apache/ignite/blob/d72a123e122ffe1b4f715f98c2db5d79293f0c90/modules/core/src/main/java/org/apache/ignite/configuration/ClientConfiguration.java

See reconnectThrottlingPeriod, reconnectThrottlingRetries.

Best regards,
Anton



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


Reconnect is not allowed due to applied throttling

2020-08-04 Thread AravindJP
Hi ,
I am getting below exception after running an Ignite client running
continuously for 48 hrs . My client is running on java (spring boot) . I am
using singleton  instance of IgniteClient object to connect and persist
data. 

Ignite version 2.8.0 

020-08-04 10:02:18.520 ERROR 1 --- [sub-subscriber3]: Exception with
org.
apache.ignite.client.ClientConnectionException: Reconnect is not allowed due
to applied throttling
at
org.apache.ignite.internal.client.thin.ReliableChannel$ClientChannelHolder.getOrCreateChannel(ReliableCha
nnel.java:448)
at
org.apache.ignite.internal.client.thin.ReliableChannel$ClientChannelHolder.getOrCreateChannel(ReliableCha
nnel.java:439)
at
org.apache.ignite.internal.client.thin.ReliableChannel$ClientChannelHolder.access$100(ReliableChannel.jav
a:395)
at
org.apache.ignite.internal.client.thin.ReliableChannel.channel(ReliableChannel.java:318)
at
org.apache.ignite.internal.client.thin.ReliableChannel.service(ReliableChannel.java:158)
at
org.apache.ignite.internal.client.thin.ReliableChannel.request(ReliableChannel.java:187)
at
org.apache.ignite.internal.client.thin.TcpClientCache.putAll(TcpClientCache.java:210)
a






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