[
https://issues.apache.org/jira/browse/IGNITE-21364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Evgeny Stanilovsky updated IGNITE-21364:
----------------------------------------
Fix Version/s: 3.2
(was: 3.1)
> Do not throw HandshakeException from MessagingService methods
> -------------------------------------------------------------
>
> Key: IGNITE-21364
> URL: https://issues.apache.org/jira/browse/IGNITE-21364
> Project: Ignite
> Issue Type: Improvement
> Components: networking
> Reporter: Roman Puchkovskiy
> Priority: Major
> Labels: ignite-3
> Fix For: 3.2
>
>
> We must guarantee that a future from send/invoke either completes
> successfully (meaning that the message was delivered to the recipient node/a
> response was received), fail with an exception that signals that the
> recipient node has left the physical topology, or fail with
> NodeStoppingException (if the sending node is stopping).
> Other outcomes seem illegal. Hence, sends/invokes cannot end up with
> HandshakeExceptions. Those must be either swallowed internally, or replaced
> with exceptions that signal that the recipient has left the physical topology.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
