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 <ptupit...@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 <sumit.deshi...@gmail.com> > wrote: > >> Correction in subject >> >> On Fri, Jul 8, 2022 at 7:12 PM Sumit Deshinge <sumit.deshi...@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
