[ 
https://issues.apache.org/jira/browse/IGNITE-21232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Roman Puchkovskiy updated IGNITE-21232:
---------------------------------------
    Description: 
# In addition to methods that use consistentId to identify the recipient, 
methods that use [ephemeral] node ID for this purpose should be added
 # Methods that accept ClusterNode should be removed
 # A method to resolve a ClusterNode by node ID should be added to 
TopologyService
 # Methods that accept consistentId must fail the send/invocation attempt (with 
same exception which is used when the target node has gone) if the resolved 
sender's destination node ID is different from the node ID specified in the 
ClusterNode obtained from the topology at the moment of the call.

  was:
# Methods of MessagingService that accept ClusterNode for recipient must fail 
the send/invocation attempt (with same exception which is used when the target 
node has gone) if the resolved sender's destination node ID is different from 
the node ID specified in the ClusterNode for recipient.
 # Methods that accept consistentId should behave in the same way: they should 
just resolve the ClusterNode by the provided consistentId and then proceed as 
in item 1


> Support sending by node ID in MessagingService
> ----------------------------------------------
>
>                 Key: IGNITE-21232
>                 URL: https://issues.apache.org/jira/browse/IGNITE-21232
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Roman Puchkovskiy
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.0.0-beta2
>
>
> # In addition to methods that use consistentId to identify the recipient, 
> methods that use [ephemeral] node ID for this purpose should be added
>  # Methods that accept ClusterNode should be removed
>  # A method to resolve a ClusterNode by node ID should be added to 
> TopologyService
>  # Methods that accept consistentId must fail the send/invocation attempt 
> (with same exception which is used when the target node has gone) if the 
> resolved sender's destination node ID is different from the node ID specified 
> in the ClusterNode obtained from the topology at the moment of the call.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to