[jira] [Commented] (RATIS-140) Raft client should reuse the gRPC stream for all async calls

["Tsz Wo Nicholas Sze (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/RATIS-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16279591#comment-16279591 ] 

Tsz Wo Nicholas Sze commented on RATIS-140:
-------------------------------------------

Agree.  The gRPC change in RATIS-113 is incorrect in the sense that it does not reuse the gRPC stream.  This JIRA is to fix this problem. 

Another problem we fix here is: when the client fails over to from an old leader to a new leader, the client should send retries in the same order.

> 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
>         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
>
>
> 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)