Hello, This case seems to be correct, it logs the event of client state updated from DISCONNECTED to RECONNECTED because the node succeeded to join the topology back within some time, the node was not segmented from the topology. What timeouts do you use in your nodes configuration?
I would suggest to perform a test with different timeouts and check that if node stays offline for too long, the node gets segmented from the topology. Best regards, Anton -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/