Hello Pavel, I have found out why the topology version keeps increasing. It's because my colleague created a customized Ignite monitor system which will fetches metrics from Ignite visor. And this monitor system will launch a Visor client connects to the cluster every minute, after fetching all the metrics from Visor it will shut down. This behavior will cause the topology version increasing. (This is a bad practice to do monitor) This is also why you're seeing the NODE_JOINED log.
Now I've stooped this monitor system and restarted cluster. This issue seems to be fixed. But we need to think is launching a Visor client connects to the cluster every minute will cause cluster freeze expected behavior? As I observed launching a Visor client connects to the cluster is not a simple operation, it usually takes more than 5 seconds to finish partition exchange and other steps before Visor is connected. Thanks for your help, Pavel. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
