[
https://issues.apache.org/jira/browse/RATIS-676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16949001#comment-16949001
]
Hadoop QA commented on RATIS-676:
---------------------------------
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 6m
37s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 7s{color}
| {color:red} RATIS-676 does not apply to master. Rebase required? Wrong
Branch? See https://yetus.apache.org/documentation/0.8.0/precommit-patchnames
for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=19.03.3 Server=19.03.3 Image:yetus/ratis:date2019-10-10 |
| JIRA Issue | RATIS-676 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12982714/RATIS-676-003.patch |
| Console output |
https://builds.apache.org/job/PreCommit-RATIS-Build/1055/console |
| Powered by | Apache Yetus 0.8.0 http://yetus.apache.org |
This message was automatically generated.
> Add a metric in RaftServer to track the Log Commit Index
> --------------------------------------------------------
>
> Key: RATIS-676
> URL: https://issues.apache.org/jira/browse/RATIS-676
> Project: Ratis
> Issue Type: Sub-task
> Components: server
> Reporter: Supratim Deka
> Assignee: Aravindan Vijayan
> Priority: Major
> Attachments: RATIS-676-000.patch, RATIS-676-001.patch,
> RATIS-676-002.patch, RATIS-676-003.patch
>
>
> RATIS-650 tracks the commit indexes of each peer in a RaftGroup - tracking is
> done as metrics on the RAFT group leader.
> This jira however tracks the RaftLog commit index as a metric of the local
> RaftServer. This metric will be reported by all nodes running a raft server
> irrespective of their role (Leader or Follower).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
