[
https://issues.apache.org/jira/browse/RATIS-651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16915784#comment-16915784
]
Shashikant Banerjee edited comment on RATIS-651 at 8/26/19 1:20 PM:
--------------------------------------------------------------------
Thanks [~avijayan] for working on this and [~elserj] for the review. I agree
that the heartBeat miss count should be aggregated in the leader. A solution
would be to take the heartBeat count outside of LeaderElection metrics and
define an new metrics for HeartBeat itself and aggregate it in the LeaderState.
[~avijayan], We can also handle heartBeat in a new Jira altogether.
was (Author: shashikant):
Thanks [~avijayan] for working on this and [~elserj] for the review. I agree
that the heartBeat miss count should be aggregated in the leader. A solution
would be to take the heartBeat count outside of LeaderElection metrics and
define an new metrics for HeartBeat itself and aggregate it in the LeaderState.
[~avijayan], We can also handle heartBeat in a new Jira altogether.
> 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)
