ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Chugunov (Jira)" <j...@apache.org>
Subject [jira] [Resolved] (IGNITE-14091) Implement messaging service
Date Wed, 30 Jun 2021 12:02:00 GMT

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

Sergey Chugunov resolved IGNITE-14091.
--------------------------------------
    Resolution: Won't Fix

First version of transport using ScaleCube transport functionality was implemented in IGNITE-14088,
this ticket is obsolete.

> Implement messaging service
> ---------------------------
>
>                 Key: IGNITE-14091
>                 URL: https://issues.apache.org/jira/browse/IGNITE-14091
>             Project: Ignite
>          Issue Type: Sub-task
>            Reporter: Anton Kalashnikov
>            Priority: Major
>              Labels: iep-66, ignite-3
>
> It needs to implement the ability to send/receive messages to/from network members:
>  * there's a requirements of being able to send idempotent messages with very weak guarantees:
>  ** no delivery guarantees required;
>  ** multiple copies of the same message might be sent;
>  ** no need to have any kind of acknowledgement;
>  * there's another requirement for the common use:
>  ** message must be sent exactly once with an acknowledgement that it has actually been
received (not necessarily processed);
>  ** messages must be received in the same order they were sent.
> These types of messages might utilize current recovery protocol with acks every 32 (or
so) messages. This setting must be flexible enough so that we won't get OOM in big topologies.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message