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/03 22:29:00 UTC
[jira] [Comment Edited] (RATIS-140) Server may see out-of-order
gRPC messages sent from the same client
[ https://issues.apache.org/jira/browse/RATIS-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16276130#comment-16276130 ]
Tsz Wo Nicholas Sze edited comment on RATIS-140 at 12/3/17 10:28 PM:
---------------------------------------------------------------------
r140_20171203.patch:
- some more bug fixes;
- changes numRequests in testSimpleWrite from 500 to 5000;
- depends on RATIS-162.
It has passed all 4 tests in TestRaftOutputStreamWithGrpc 99 times.
was (Author: szetszwo):
r140_20171203.patch:
- some more bug fixes;
- changes numRequests in testSimpleWrite from 500 to 5000.
It has passed all 4 tests in TestRaftOutputStreamWithGrpc 99 times.
> Server may see out-of-order gRPC messages sent from the same client
> -------------------------------------------------------------------
>
> 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
> Attachments: r140_20171123.patch, r140_20171124.patch, r140_20171125.patch, r140_20171126.patch, r140_20171126b.patch, r140_20171130.patch, r140_20171203.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)