[
https://issues.apache.org/jira/browse/RATIS-650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16941527#comment-16941527
]
Hadoop QA commented on RATIS-650:
---------------------------------
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} docker {color} | {color:red} 0m
6s{color} | {color:red} Docker failed to build yetus/ratis:date2019-10-01.
{color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | RATIS-650 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12981849/RATIS-650.005.patch |
| Console output |
https://builds.apache.org/job/PreCommit-RATIS-Build/1015/console |
| Powered by | Apache Yetus 0.8.0 http://yetus.apache.org |
This message was automatically generated.
> Add metrics to track commit index of each peer in a RaftGroup
> -------------------------------------------------------------
>
> Key: RATIS-650
> URL: https://issues.apache.org/jira/browse/RATIS-650
> Project: Ratis
> Issue Type: Sub-task
> Components: server
> Reporter: Shashikant Banerjee
> Assignee: Supratim Deka
> Priority: Major
> Fix For: 0.5.0
>
> Attachments: RATIS-650.000.patch, RATIS-650.002.patch,
> RATIS-650.003.patch, RATIS-650.004.patch, RATIS-650.005.patch
>
>
> Tracking the RaftLog commit index on each peer in a RaftGroup is useful to
> monitor the performance of the group.
> Simply as an illustrative example : whenever a specific peer starts to lag
> behind the majority, the problem becomes visible to the monitoring agent even
> before the slow follower detection mechanism on the Leader kicks in.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
