You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Maxim Muzafarov (JIRA)" <ji...@apache.org> on 2019/01/25 07:55:00 UTC
[jira] [Updated] (IGNITE-10619) Add support for nio channel
connections over CommunicationSpi
[ https://issues.apache.org/jira/browse/IGNITE-10619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maxim Muzafarov updated IGNITE-10619:
-------------------------------------
Summary: Add support for nio channel connections over CommunicationSpi (was: Add support for ReadableByteChannel, WritableByteChannel over CommunicationSpi)
> Add support for nio channel connections over CommunicationSpi
> -------------------------------------------------------------
>
> Key: IGNITE-10619
> URL: https://issues.apache.org/jira/browse/IGNITE-10619
> Project: Ignite
> Issue Type: Sub-task
> Components: persistence
> Reporter: Maxim Muzafarov
> Assignee: Maxim Muzafarov
> Priority: Major
> Labels: iep-28
>
> To benefit from zero copy we must delegate the file transferring to FileChannel#transferTo(long, long, java.nio.channels.WritableByteChannel) because the fast path of transferTo method is only executed if the destination buffer inherits from an internal JDK class.
> The {{CommunicationSpi}} needs to support pipe connections between two nodes;
> * The WritableByteChannel needs to be accessed on the supplier side;
> * The ReadableByteChannel needs to be read on the demander side;
> * The CommunicationListener must be extended to respond on new incoming pipe connections;
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)