You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by Sumit Deshinge <su...@gmail.com> on 2022/07/08 13:44:48 UTC

Re: Thin client cache operations takes longer and longer for subsequent retries to throw exception when server down

Correction in subject

On Fri, Jul 8, 2022 at 7:12 PM Sumit Deshinge <su...@gmail.com>
wrote:

> Hi,
>
> I have ignite thin clients connecting to ignite server.
> When server node is down, ClientCache operations like get, exists takes
> incremental times to throw clientconnectiontimeout exception. e.g. 40s,
> 60s, 80s, ... upto ~600s and then again it starts with around 40s time for
> response.
>
> Which setting/property do I need to change in order to reduce this time?
> Basically I want these client cache operations to fail fast during
> subsequent retries.
>
> --
> Regards,
> Sumit Deshinge
>
>

-- 
Regards,
Sumit Deshinge

Re: Thin client cache operations takes longer and longer for subsequent retries to throw exception when server down

Posted by Sumit Deshinge <su...@gmail.com>.
Hi Pavel,

Thanks for pointing this out. I will try them out and get back to you if
required.

On Fri, Jul 8, 2022 at 11:42 PM Pavel Tupitsyn <pt...@apache.org> wrote:

> This behavior is controlled by the following fields in ClientConfiguration
> [1]:
> retryLimit, reconnectThrottlingRetries, reconnectThrottlingPeriod
>
> To fail fast, set reconnectThrottlingPeriod to 0 and retryLimit to 1.
>
> [1]
> https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/configuration/ClientConfiguration.html
>
> On Fri, Jul 8, 2022 at 4:46 PM Sumit Deshinge <su...@gmail.com>
> wrote:
>
>> Correction in subject
>>
>> On Fri, Jul 8, 2022 at 7:12 PM Sumit Deshinge <su...@gmail.com>
>> wrote:
>>
>>> Hi,
>>>
>>> I have ignite thin clients connecting to ignite server.
>>> When server node is down, ClientCache operations like get, exists takes
>>> incremental times to throw clientconnectiontimeout exception. e.g. 40s,
>>> 60s, 80s, ... upto ~600s and then again it starts with around 40s time for
>>> response.
>>>
>>> Which setting/property do I need to change in order to reduce this time?
>>> Basically I want these client cache operations to fail fast during
>>> subsequent retries.
>>>
>>> --
>>> Regards,
>>> Sumit Deshinge
>>>
>>>
>>
>> --
>> Regards,
>> Sumit Deshinge
>>
>>

-- 
Regards,
Sumit Deshinge

Re: Thin client cache operations takes longer and longer for subsequent retries to throw exception when server down

Posted by Pavel Tupitsyn <pt...@apache.org>.
This behavior is controlled by the following fields in ClientConfiguration
[1]:
retryLimit, reconnectThrottlingRetries, reconnectThrottlingPeriod

To fail fast, set reconnectThrottlingPeriod to 0 and retryLimit to 1.

[1]
https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/configuration/ClientConfiguration.html

On Fri, Jul 8, 2022 at 4:46 PM Sumit Deshinge <su...@gmail.com>
wrote:

> Correction in subject
>
> On Fri, Jul 8, 2022 at 7:12 PM Sumit Deshinge <su...@gmail.com>
> wrote:
>
>> Hi,
>>
>> I have ignite thin clients connecting to ignite server.
>> When server node is down, ClientCache operations like get, exists takes
>> incremental times to throw clientconnectiontimeout exception. e.g. 40s,
>> 60s, 80s, ... upto ~600s and then again it starts with around 40s time for
>> response.
>>
>> Which setting/property do I need to change in order to reduce this time?
>> Basically I want these client cache operations to fail fast during
>> subsequent retries.
>>
>> --
>> Regards,
>> Sumit Deshinge
>>
>>
>
> --
> Regards,
> Sumit Deshinge
>
>