[jira] [Commented] (RATIS-632) Leader should throw ResourceUnavailableException when follower lags in commit index

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

[jira] [Commented] (RATIS-631) Propagate state machine's last applied index from follower to leader

[ https://issues.apache.org/jira/browse/RATIS-631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17021805#comment-17021805 ] Tsz-wo Sze commented on RATIS-631: -- The last applied index is not used in the patch. What is the plan?

[jira] [Commented] (RATIS-632) Leader should throw ResourceUnavailableException when follower lags in commit index

[ https://issues.apache.org/jira/browse/RATIS-632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17021804#comment-17021804 ] Tsz-wo Sze commented on RATIS-632: -- Could you describe the cases that we will reject a client request? >

[jira] [Commented] (RATIS-795) Read SateMachine data failure should result in log fail notification

[ https://issues.apache.org/jira/browse/RATIS-795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17021370#comment-17021370 ] Siddharth Wagle commented on RATIS-795: --- Hi [~shashikant], thanks for the review, I ran all the

[jira] [Commented] (RATIS-796) Add watch time out for Ratis Client

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

[jira] [Commented] (RATIS-799) Add a new retry policy Exception dependent retry policy

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

[jira] [Commented] (RATIS-755) Add a log dump command line utility inside ratis

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

[jira] [Commented] (RATIS-794) Ratils leader should retry append requests based on follower commit info in case of intermittent append failures

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

[jira] [Commented] (RATIS-796) Add watch time out for Ratis Client

[ https://issues.apache.org/jira/browse/RATIS-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17021028#comment-17021028 ] Shashikant Banerjee commented on RATIS-796: --- Thanks [~bharat] for working in this. 

[jira] [Commented] (RATIS-795) Read SateMachine data failure should result in log fail notification

[ https://issues.apache.org/jira/browse/RATIS-795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17021019#comment-17021019 ] Shashikant Banerjee commented on RATIS-795: --- Thanks [~swagle] for working on this. The patch

[jira] [Updated] (RATIS-794) Ratils leader should retry append requests based on follower commit info in case of intermittent append failures

[ https://issues.apache.org/jira/browse/RATIS-794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz-wo Sze updated RATIS-794: - Attachment: r794_20200122.patch > Ratils leader should retry append requests based on follower commit