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 2019/11/29 00:23:00 UTC

[jira] [Updated] (RATIS-729) Add an assertion in ClientProtoUtils#toRaftClientReplyProto

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

Tsz-wo Sze updated RATIS-729:
-----------------------------
    Summary: Add an assertion in ClientProtoUtils#toRaftClientReplyProto  (was: ClientProtoUtils#toRaftClientReplyProto should consider all RaftException types)

> Add an assertion in ClientProtoUtils#toRaftClientReplyProto
> -----------------------------------------------------------
>
>                 Key: RATIS-729
>                 URL: https://issues.apache.org/jira/browse/RATIS-729
>             Project: Ratis
>          Issue Type: Bug
>          Components: client
>            Reporter: Lokesh Jain
>            Assignee: Hanisha Koneru
>            Priority: Major
>         Attachments: RATIS-729.001.patch, RATIS-729.002.patch, RATIS-729.003.patch, RATIS-729.004.patch, RATIS-729.005.patch
>
>
> In one of the runs it is seen that client receives RaftClientReply with exception as null and success flag as false. This happens because currently ClientProtoUtils#toRaftClientReplyProto only considers a few RaftException types while creating a RaftClientReplyProto. We should also add handling for other exception types.Similar changes will be required in ClientProtoUtils#toRaftClientReply.
> We will also need to add handling for these exceptions in the client code.



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