[
https://issues.apache.org/jira/browse/RATIS-651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16914608#comment-16914608
]
Josh Elser commented on RATIS-651:
----------------------------------
The change to LogAppender makes sense to catch from any Peer, but this leaves
an aggregation problem. It would be nice if the Leader could be reporting the
last hearbeat (empty AppendEntries) so that we can have a clear "this is the
last time I heard from each group member" in a single place.
Looking through LogAppender, I'm not seeing a place where we actually track
this in the leader, so that might be something that requires more plumbing
before it can be instrumented with metrics?
> Add metrics related to leaderElection and HeartBeat
> ---------------------------------------------------
>
> Key: RATIS-651
> URL: https://issues.apache.org/jira/browse/RATIS-651
> Project: Ratis
> Issue Type: Sub-task
> Components: server
> Affects Versions: 0.4.0
> Reporter: Shashikant Banerjee
> Assignee: Aravindan Vijayan
> Priority: Major
> Attachments: RATIS-651-000.patch
>
>
> Following metrics would be helpful to determine the leader election events
> and timeouts:
>
> |numLeaderElections|Number of leader elections since the creation of ratis
> pipeline|
> |numLeaderElectionTimeouts|Number of leader election timeouts or failures|
> |LeaderElectionCompletionLatency|Time required to complete a leader election|
> |MaxNoLeaderInterval|Max time where there has been no elected leader in the
> raft ring|
> |heartBeatMissCount|No of times heartBeat response is missed from a server |
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
