You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ratis.apache.org by "Tsz Wo Nicholas Sze (JIRA)" <ji...@apache.org> on 2019/01/11 06:24:00 UTC
[jira] [Updated] (RATIS-167) Implement a high performance
OutputStream using async API
[ https://issues.apache.org/jira/browse/RATIS-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tsz Wo Nicholas Sze updated RATIS-167:
--------------------------------------
Attachment: r167_20190111.patch
> Implement a high performance OutputStream using async API
> ---------------------------------------------------------
>
> Key: RATIS-167
> URL: https://issues.apache.org/jira/browse/RATIS-167
> Project: Ratis
> Issue Type: New Feature
> Components: client
> Reporter: Tsz Wo Nicholas Sze
> Assignee: Tsz Wo Nicholas Sze
> Priority: Major
> Labels: ozone
> Attachments: r167_20180921.patch, r167_20181109.patch, r167_20181207.patch, r167_20181210.patch, r167_20190111.patch
>
>
> With an in-order async API, it is easy to implement a high performance OutputStream.
> Also, since the async API already takes care leader change, the OutputStream implementation supports automatic failover for free.
> The code is generic in the sense that it is RPC independent (as long as the RPC supports in-order async API).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)