ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From vkulichenko <valentin.kuliche...@gmail.com>
Subject Re: Client fails to connect - joinTimeout vs networkTimeout
Date Thu, 21 Apr 2016 20:07:15 GMT
Hi Binti,

1. networkTimeout , ackTimeout and maxAckTimeout are legacy settings and I
would recommend to use failure detection timeout instead [1]. This is a
global setting that defines the period of time during which a node can be
unaccessible before being considered failed. joinTimeout on the other side
defines how long node waits for discovery during startup. If discovery
doesn't happen, there can be different reasons. I would check server logs
and network load first.
2. What do you expect from the client in this case? Client can't actually
work without servers, even if it start, it will throw an exception on any
operation.
3. TcpDiscoverySpi and TcpCommunicationSpi are different components and are
used by any node (client or server) in parallel for different purposes. The
failure detection timeout is properly applied to both of them.

[1]
https://apacheignite.readme.io/docs/cluster-config#failure-detection-timeout

-Val



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Client-fails-to-connect-joinTimeout-vs-networkTimeout-tp4419p4431.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Mime
View raw message