Hi Jayaram, If client node disconnect from the server topology, it will reconnect when the network connection is restored. Note that when it's disconnected, any API call will throw special IgniteClientDisconnectedException that has reconnectFuture() method. It gives a future that will be completed when the reconnection happens.
If the server topology itself is segmented, then you will have two independent clusters which can't be merged without losing data consistency. You will have to stop one of them and start again when connection is restored. They will rejoin the topology and rebalance the data. BTW, GridGain Enterprise provides capabilities for automatic resolution of such cases [1]. [1] https://gridgain.readme.io/docs/network-segmentation -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-cluster-recovery-after-network-partition-tp2775p2778.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
