[ https://issues.apache.org/jira/browse/RATIS-729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16973610#comment-16973610 ]
Tsz-wo Sze commented on RATIS-729: ---------------------------------- > ... the client receives a RaftClientReply with success flag as false and with > exception set as null. ... This sounds like a bug needed to be fixed. Could you describe how to reproduce it? > For undesired exceptions we can throw an exception in the raft client? Yes. For example, if there is a SocketException, we may throw/completeExceptionally it. > ClientProtoUtils#toRaftClientReplyProto should consider all RaftException > types > ------------------------------------------------------------------------------- > > Key: RATIS-729 > URL: https://issues.apache.org/jira/browse/RATIS-729 > Project: Ratis > Issue Type: Bug > Reporter: Lokesh Jain > Assignee: Hanisha Koneru > Priority: Major > Attachments: RATIS-729.001.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)