and client will use timeout of 10 seconds.
>>
>> Stan
>>
>> From: Valentin Kulichenko
>> Sent: 6 июля 2018 г. 23:17
>> To: dev@ignite.apache.org
>> Subject: Re: IgniteConfiguration, TcpDiscoverySpi,
>> TcpCommunicationSpitimeouts
>>
>> Stan,
>
onTimeout=20.
> When these two nodes communicate, server will use timeouts of 20 seconds
> and client will use timeout of 10 seconds.
>
> Stan
>
> From: Valentin Kulichenko
> Sent: 6 июля 2018 г. 23:17
> To: dev@ignite.apache.org
> Subject: Re: IgniteConfiguration, TcpDiscoveryS
seconds and
client will use timeout of 10 seconds.
Stan
From: Valentin Kulichenko
Sent: 6 июля 2018 г. 23:17
To: dev@ignite.apache.org
Subject: Re: IgniteConfiguration, TcpDiscoverySpi, TcpCommunicationSpitimeouts
Stan,
Can you explain the semantics of both parameters? How do they behave when
set
ients instead of
> > failureDetectionTimeout
> > *What*: change code to use clientFailureDetectionTimeout on clients
> > *When*: update code and readme.io docs in 2.7
> >
> > Thanks,
> > Stan
> >
> > From: Valentin Kulichenko
> > Sent: 30 мая
Kulichenko
Sent: 5 июля 2018 г. 18:16
To: dev@ignite.apache.org
Subject: Re: IgniteConfiguration, TcpDiscoverySpi, TcpCommunicationSpitimeouts
Stan,
What is the purpose of clientFailureDetectionTimeout? Why can't we just
always use failureDetectionTimeout? Is there any difference between these
two
IgniteConfiguration neither of
> > which we’re considering for deprecation and removal in 3.0.
> >
> > Stan
> >
> > From: Valentin Kulichenko
> > Sent: 29 мая 2018 г. 22:17
> > To: dev@ignite.apache.org
> > Subject: Re: IgniteConfiguration, Tcp
: IgniteConfiguration, TcpDiscoverySpi, TcpCommunicationSpitimeouts
Stan,
Looks like you suggest to only change the default. If so, it's OK. But
let's not change the behavior of these timeouts for the case they are
explicitly set in config.
Thanks,
Val
On Wed, May 30, 2018 at 1:06 AM, Stanislav
eConfiguration neither of
> which we’re considering for deprecation and removal in 3.0.
>
> Stan
>
> From: Valentin Kulichenko
> Sent: 29 мая 2018 г. 22:17
> To: dev@ignite.apache.org
> Subject: Re: IgniteConfiguration, TcpDiscoverySpi,
> TcpCommunicationSpiti
in IgniteConfiguration neither of which
we’re considering for deprecation and removal in 3.0.
Stan
From: Valentin Kulichenko
Sent: 29 мая 2018 г. 22:17
To: dev@ignite.apache.org
Subject: Re: IgniteConfiguration, TcpDiscoverySpi, TcpCommunicationSpitimeouts
Stan,
OK, I got confused a little :)
I do agree
g the changes.
>
> Thanks,
> Stan
>
> From: Valentin Kulichenko
> Sent: 29 мая 2018 г. 0:57
> To: dev@ignite.apache.org
> Subject: Re: IgniteConfiguration, TcpDiscoverySpi,
> TcpCommunicationSpitimeouts
>
> Hi Stan,
>
> I'm 100% for this activity, however I
10 matches
Mail list logo
