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 2017/12/06 08:14:00 UTC

[jira] [Comment Edited] (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:comment-tabpanel&focusedCommentId=16279790#comment-16279790 ] 

Tsz Wo Nicholas Sze edited comment on RATIS-167 at 12/6/17 8:13 AM:
--------------------------------------------------------------------

r167_20171206.patch: split from (and depends on) RATIS-140.


was (Author: szetszwo):
r167_20171206.patch: split from RATIS-140.

> 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
>            Reporter: Tsz Wo Nicholas Sze
>            Assignee: Tsz Wo Nicholas Sze
>         Attachments: r167_20171206.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
(v6.4.14#64029)