[
https://issues.apache.org/jira/browse/IGNITE-21365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Puchkovskiy updated IGNITE-21365:
---------------------------------------
Description:
# It must be clearly stated that for normal messages (if message's needsAck()
returns true), send/invoke will provide ordering guarantees
# For normal messages, the only possible outcomes are:
## Successful delivery (and future completion)
## (Only for invokes): timeout
## Exception signalling that the recipient has left the physical topology
## NodeStoppingException if current node stops
# For normal messages, the above guarantees are provided even in cases when a
physical connection is closed: another one would be open and proceed servicing
the logical conneciton
# For non-normal (non-ackable) messages, those guarantees are not guaranteed
> Improve documentation on MessagingService
> -----------------------------------------
>
> Key: IGNITE-21365
> URL: https://issues.apache.org/jira/browse/IGNITE-21365
> Project: Ignite
> Issue Type: Improvement
> Reporter: Roman Puchkovskiy
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
>
> # It must be clearly stated that for normal messages (if message's needsAck()
> returns true), send/invoke will provide ordering guarantees
> # For normal messages, the only possible outcomes are:
> ## Successful delivery (and future completion)
> ## (Only for invokes): timeout
> ## Exception signalling that the recipient has left the physical topology
> ## NodeStoppingException if current node stops
> # For normal messages, the above guarantees are provided even in cases when
> a physical connection is closed: another one would be open and proceed
> servicing the logical conneciton
> # For non-normal (non-ackable) messages, those guarantees are not guaranteed
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
