Hi Biren, What is the use case and what are you trying to achieve by all this?
First of all, there is a difference between node_left/failed and node_segmented events. The former is fired on nodes that are still in topology to notify that one of the nodes left or failed. But the latter means that *local* node got segmented, and I don't think it makes sense to do any checks there. Segmentation can happen for various reasons, but in vast majority of cases it's a long GC pause. In this case node does not close connections, but becomes unresponsive, which causes the cluster to remove it from topology after failure detection timeout. When GC pause finishes, node tries to continue to operate, but realizes that it was already kicked out. It then fires node_segmented event locally and stops immediately. This is correct behavior. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Cluster-segmentation-tp16314p16351.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
