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 Sze (Jira)" <ji...@apache.org> on 2020/11/11 12:43:00 UTC

[jira] [Updated] (RATIS-1148) In NettyServerStreamRpc, each remote stream should not wait for its previous write

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

Tsz-wo Sze updated RATIS-1148:
------------------------------
    Description: In RATIS-1145, we changed the remote stream to wait for its own previous write.  Indeed, the remote streams should just submit the async calls.  Then, the sliding window will take care the async calls.  (was: In RATIS-1145, we changed all the remote writes to wait for the previous reply.  Indeed, the remote writes should just submit the async calls.  Then, the sliding window will take care the async calls.)
        Summary: In NettyServerStreamRpc, each remote stream should not wait for its previous write  (was: In NettyServerStreamRpc, the remote writes should not wait for the previous reply)

> In NettyServerStreamRpc, each remote stream should not wait for its previous write
> ----------------------------------------------------------------------------------
>
>                 Key: RATIS-1148
>                 URL: https://issues.apache.org/jira/browse/RATIS-1148
>             Project: Ratis
>          Issue Type: Sub-task
>          Components: Netty, server, Streaming
>            Reporter: Tsz-wo Sze
>            Assignee: Tsz-wo Sze
>            Priority: Major
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> In RATIS-1145, we changed the remote stream to wait for its own previous write.  Indeed, the remote streams should just submit the async calls.  Then, the sliding window will take care the async calls.



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