Hi Alper, I'm not sure I understand the issue and the fix.
EVT_NODE_LEFT/FAILED and EVT_CLIENT_NODE_DISCONNECTED are different events that are fired in different situations. For example, EVT_CLIENT_NODE_DISCONNECTED can happen due to network outage, even without any server failures. And on the other hand it will not happen if the servers it was physically connected dies, but the client immediately restores the connection with the cluster through another server. Having said that, if you need to know when the server left or failed, you should listen for EVT_NODE_LEFT/FAILED events. You will receive events for clients as well, but that's OK, because DiscoveryEvent contains ClusterNode instance that has all the information about the failed node. I.e., you can filter out by ClusterNode.isClient() flag. Makes sense? -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Re-Server-node-info-when-client-disconnects-tp3562p3585.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
