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 2018/01/09 07:56:00 UTC
[jira] [Commented] (RATIS-140) Raft client should reuse the gRPC
stream for all async calls
[ https://issues.apache.org/jira/browse/RATIS-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16317948#comment-16317948 ]
Tsz Wo Nicholas Sze commented on RATIS-140:
-------------------------------------------
Filed RATIS-188 for supporting size limitation inside SlidingWindow
> Raft client should reuse the gRPC stream for all async calls
> ------------------------------------------------------------
>
> Key: RATIS-140
> URL: https://issues.apache.org/jira/browse/RATIS-140
> Project: Ratis
> Issue Type: Bug
> Reporter: Tsz Wo Nicholas Sze
> Assignee: Tsz Wo Nicholas Sze
> Fix For: 0.2.0-alpha
>
> Attachments: r140_20171123.patch, r140_20171124.patch, r140_20171125.patch, r140_20171126.patch, r140_20171126b.patch, r140_20171130.patch, r140_20171203.patch, r140_20171204.patch, r140_20171206.patch, r140_20171210.patch, r140_20171219.patch
>
>
> Async client is being added in RATIS-113. However, we found that the server side (RaftClientProtocolService) may see out-of-order grpc messages even if all messages are sent by the same client.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)