Hi, If one of the nodes (client or server) leaves or fails, discovery component will notify everyone else about this. However, this is not happening momentarily, so there is a time gap between actual failure and discovery notification. If a message is sent within this gap, it will end up with exception like this. Having said that, there is nothing additional required from your side, but you can probably handle the exception.
-Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Failed-to-send-message-to-remote-node-error-when-remote-node-has-been-terminated-tp9021p9026.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
