[jira] [Commented] (RATIS-677) Log entry marked corrupt due to ChecksumException

[ https://issues.apache.org/jira/browse/RATIS-677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16983234#comment-16983234 ] Sammi Chen commented on RATIS-677: -- Hi [~szetszwo], is the fix in Ozone master branch already? I saw

[jira] [Commented] (RATIS-709) RaftClient should not retry on a different leader on NotReplicated exception from leader

[ https://issues.apache.org/jira/browse/RATIS-709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16982773#comment-16982773 ] Hadoop QA commented on RATIS-709: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Commented] (RATIS-709) RaftClient should not retry on a different leader on NotReplicated exception from leader

[ https://issues.apache.org/jira/browse/RATIS-709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16982750#comment-16982750 ] Tsz-wo Sze commented on RATIS-709: -- +1 the 00 patch looks good. Pending Jenkins. > RaftClient should

[jira] [Updated] (RATIS-759) Support stream APIs to send large messages

[ https://issues.apache.org/jira/browse/RATIS-759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz-wo Sze updated RATIS-759: - Summary: Support stream APIs to send large messages (was: Support a stream method to send large

[jira] [Commented] (RATIS-756) Fix identified names in ratis-common

[ https://issues.apache.org/jira/browse/RATIS-756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16982740#comment-16982740 ] Tsz-wo Sze commented on RATIS-756: -- > ... If you still feel some more changes are needed, pls give me a

[jira] [Commented] (RATIS-729) ClientProtoUtils#toRaftClientReplyProto should consider all RaftException types

[ https://issues.apache.org/jira/browse/RATIS-729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16982722#comment-16982722 ] Hanisha Koneru commented on RATIS-729: -- Thanks [~ljain], I did think we need to log that case too but

[jira] [Created] (RATIS-761) Handle writeStateMachineData failure in leader

Lokesh Jain created RATIS-761: - Summary: Handle writeStateMachineData failure in leader Key: RATIS-761 URL: https://issues.apache.org/jira/browse/RATIS-761 Project: Ratis Issue Type: Bug

[jira] [Updated] (RATIS-709) RaftClient should not retry on a different leader on NotReplicated exception from leader

[ https://issues.apache.org/jira/browse/RATIS-709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sammi Chen updated RATIS-709: - Attachment: RATIS-709.00.patch > RaftClient should not retry on a different leader on NotReplicated

[jira] [Commented] (RATIS-729) ClientProtoUtils#toRaftClientReplyProto should consider all RaftException types

[ https://issues.apache.org/jira/browse/RATIS-729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16982236#comment-16982236 ] Lokesh Jain commented on RATIS-729: --- {code:java} +if (r.getException() != null) { {code}