[
https://issues.apache.org/jira/browse/RATIS-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16333617#comment-16333617
]
Ted Yu commented on RATIS-140:
------------------------------
nit:
{code}
+ if (e instanceof CompletionException) {
+ e = e.getCause();
+ }
+ if (e instanceof GroupMismatchException) {
+ throw new CompletionException(e);
{code}
If e was already an instance of CompletionException with GroupMismatchException
as cause for the first if, the second if would create an equivalent
CompletionException as the original e.
> 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
> Priority: Major
> 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
(v7.6.3#76005)
