You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Nikolay Tikhonov (JIRA)" <ji...@apache.org> on 2015/07/29 18:22:09 UTC

[jira] [Commented] (IGNITE-1169) Need to add TcpCommunicationSpi.sendWithAck

    [ https://issues.apache.org/jira/browse/IGNITE-1169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14646345#comment-14646345 ] 

Nikolay Tikhonov commented on IGNITE-1169:
------------------------------------------

Implemented {{sendWithAck}} method on {{TcpCommunicationSpi}} that returns {{IgniteInternalFuture}}. This future gets completed when GridNioRecoveryDescriptor received ack message.

> Need to add TcpCommunicationSpi.sendWithAck
> -------------------------------------------
>
>                 Key: IGNITE-1169
>                 URL: https://issues.apache.org/jira/browse/IGNITE-1169
>             Project: Ignite
>          Issue Type: New Feature
>            Reporter: Yakov Zhdanov
>            Assignee: Nikolay Tikhonov
>            Priority: Critical
>
> Communication uses internal acks to manage connection recovery queues in order not to miss messages on connection problems.
> We need to add TcpCommunicationSpi.sendWithAck that returns future which gets completed when node sends communication ack back.
> Use case:
> Sometimes we need to send messages and know for sure that message has been delivered (not processed - this is stronger requirement). So, we can use communication ack not to introduce top-level protocol acks. This can be used, for example, to make sure that client has received continuous query notification.
> Brief list of changes:
> * TcpCommunicationSpi - add sendWithAck() method, implement notification logic on top of existing acks
> * IoManager - add ability to send ordered and unordered messages with ack and get notification on peer receiving the message.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)