My application nodes are running on VMs and observing that topology version
is changing very frequently but I do not see any error/exceptions/warnings
in log files.

For ignite I have kept the log level to WARN.

Timeout settings in millis are as follows:

FailureDetectionTimeout = 120000
NetworkTimeout = 10000
ClientFailureDetectionTimeout = 120000

1) Does the topology version change when node becomes unreachable and
becomes reachable again within the failure detection time out?

2) Which time out setting does ignite use  while deciding that topology
version is changed?

3) Why the node is not getting segmented in this case? Is it because the
node is becoming reachable within failure detection timeout?

4) What is the purpose of network timeout ?


*App Logs::*



*Topology snapshot [ver=18, servers=4, clients=6, CPUs=172, offheap=40.0GB,
heap=160.0GB]Topology snapshot [ver=19, servers=4, clients=5, CPUs=152,
offheap=40.0GB, heap=140.0GB]Topology snapshot [ver=20, servers=4,
clients=4, CPUs=132, offheap=40.0GB, heap=130.0GB] *
*...*
*..*




*.Topology snapshot [ver=56, servers=4, clients=4, CPUs=132,
offheap=40.0GB, heap=130.0GB]Topology snapshot [ver=57, servers=4,
clients=5, CPUs=152, offheap=40.0GB, heap=140.0GB]Topology snapshot
[ver=58, servers=4, clients=4, CPUs=132, offheap=40.0GB,
heap=130.0GB]Topology snapshot [ver=59, servers=4, clients=5, CPUs=152,
offheap=40.0GB, heap=140.0GB] *

Reply via email to