[jira] [Commented] (RATIS-650) Add metric to track lag between leader and follower in Log commit

[ https://issues.apache.org/jira/browse/RATIS-650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16923141#comment-16923141 ] Shashikant Banerjee commented on RATIS-650: --- Thanks [~sdeka] for working on this

[jira] [Updated] (RATIS-650) Add metric to track lag between leader and follower in Log commit

[ https://issues.apache.org/jira/browse/RATIS-650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supratim Deka updated RATIS-650: Attachment: (was: RATIS-650.001.patch) > Add metric to track lag between leader and follower in

[jira] [Updated] (RATIS-650) Add metric to track lag between leader and follower in Log commit

[ https://issues.apache.org/jira/browse/RATIS-650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supratim Deka updated RATIS-650: Attachment: RATIS-650.001.patch > Add metric to track lag between leader and follower in Log commit

[jira] [Updated] (RATIS-650) Add metric to track lag between leader and follower in Log commit

[ https://issues.apache.org/jira/browse/RATIS-650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supratim Deka updated RATIS-650: Attachment: RATIS-650.002.patch > Add metric to track lag between leader and follower in Log commit

[jira] [Commented] (RATIS-650) Add metric to track lag between leader and follower in Log commit

[ https://issues.apache.org/jira/browse/RATIS-650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16923261#comment-16923261 ] Supratim Deka commented on RATIS-650: - Thanks for the code review [~shashikant] Change

[jira] [Commented] (RATIS-670) Add a metric to track the lag between Log commit and Log apply index

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

[jira] [Commented] (RATIS-556) Detect node failures and close the log to prevent additional writes

[ https://issues.apache.org/jira/browse/RATIS-556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16923280#comment-16923280 ] Josh Elser commented on RATIS-556: -- Awesome, thanks Rajesh! > Detect node failures and c

[jira] [Commented] (RATIS-650) Add metric to track lag between leader and follower in Log commit

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

[jira] [Commented] (RATIS-619) Avoid loading cache with pre-snapshot entries for the group

[ https://issues.apache.org/jira/browse/RATIS-619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16923667#comment-16923667 ] Tsz Wo Nicholas Sze commented on RATIS-619: --- > If here if the leader restart, th

[jira] [Commented] (RATIS-672) Vagrant test's Maven 404's

[ https://issues.apache.org/jira/browse/RATIS-672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16923728#comment-16923728 ] Josh Elser commented on RATIS-672: -- {quote}We should point to an {{archive.apache.org}} U

[jira] [Commented] (RATIS-672) Vagrant test's Maven 404's

[ https://issues.apache.org/jira/browse/RATIS-672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16923787#comment-16923787 ] Clay B. commented on RATIS-672: --- We don't need a specific Maven version -- but it seems pain

[jira] [Commented] (RATIS-672) Vagrant test's Maven 404's

[ https://issues.apache.org/jira/browse/RATIS-672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16923789#comment-16923789 ] Josh Elser commented on RATIS-672: -- Yeah, checksums are not on mirrors. They need to be p

[jira] [Commented] (RATIS-672) Vagrant test's Maven 404's

[ https://issues.apache.org/jira/browse/RATIS-672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16923792#comment-16923792 ] Josh Elser commented on RATIS-672: -- It may be just fine to pull from archive.a.o fwiw. Ju

[jira] [Commented] (RATIS-619) Avoid loading cache with pre-snapshot entries for the group

[ https://issues.apache.org/jira/browse/RATIS-619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16923911#comment-16923911 ] Mukul Kumar Singh commented on RATIS-619: - Yes, how about we divide this into 2 ta

[jira] [Updated] (RATIS-569) StatusRuntimeException on the datanode because clients do not shutdown the observer cleanly.

[ https://issues.apache.org/jira/browse/RATIS-569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle updated RATIS-569: -- Attachment: RATIS-569.03.patch > StatusRuntimeException on the datanode because clients do not s

[jira] [Updated] (RATIS-569) StatusRuntimeException on the datanode because clients do not shutdown the observer cleanly.

[ https://issues.apache.org/jira/browse/RATIS-569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle updated RATIS-569: -- Attachment: RATIS-569.03.patch > StatusRuntimeException on the datanode because clients do not s

[jira] [Updated] (RATIS-569) StatusRuntimeException on the datanode because clients do not shutdown the observer cleanly.

[ https://issues.apache.org/jira/browse/RATIS-569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle updated RATIS-569: -- Attachment: (was: RATIS-569.03.patch) > StatusRuntimeException on the datanode because clien

[jira] [Commented] (RATIS-569) StatusRuntimeException on the datanode because clients do not shutdown the observer cleanly.

[ https://issues.apache.org/jira/browse/RATIS-569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16923923#comment-16923923 ] Siddharth Wagle commented on RATIS-569: --- Verified the changes by manually running Mi

[jira] [Commented] (RATIS-569) StatusRuntimeException on the datanode because clients do not shutdown the observer cleanly.

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