Check the logs of all your servers nodes and client applications, you should see why the nodes stop and start. The topology changes only if a node leaves the cluster or joins it.
The failureDetectionTimeout is used by default for the network communication timeouts between the nodes: https://apacheignite.readme.io/docs/tcpip-discovery#section-failure-detection-timeout - Denis On Tue, Dec 10, 2019 at 10:30 PM Prasad Bhalerao < [email protected]> wrote: > Can you please try to answer question 1, 2 and 3? > > In my logs I could see that number of server are also changing. Topology > version changes when server node becomes 3 and again becomes 4. Total > number of server nodes are 4. > > Thanks, > Prasad > > > On Tue 10 Dec, 2019, 11:45 PM akurbanov <[email protected] wrote: > >> Hello, >> >> Are you able to share full logs from the server and client instances? >> >> In short: by default clients can reconnect to the cluster after the >> network >> connection was disrupted by anything (network issues, gc pauses etc.). >> >> >> https://apacheignite.readme.io/docs/clients-vs-servers#section-reconnecting-a-client >> >> Server drops client node from topology once failure detection timeout is >> reached, if you want a client to be stopped and segmented in this case, >> use >> property clientReconnectDisabled and set it to true, the sample is on the >> documentation page. >> >> Network timeout defines the timeout for different network operations, >> among >> the usages are client reconnect attempt timeout, connection establishing >> timeout on join attempt and sending messages. >> >> Best regards, >> Anton >> >> >> >> -- >> Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >> >
