[
https://issues.apache.org/jira/browse/RATIS-670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926835#comment-16926835
]
Supratim Deka edited comment on RATIS-670 at 9/10/19 6:44 PM:
--------------------------------------------------------------
patch 001, added a gauge to directly get the value of applied index, instead of
recording diff with commitIndex.
this is as per review discussion with [~shashikant] and mukul.
was (Author: sdeka):
patch 002, added a gauge to directly get the value of applied index, instead of
recording diff with commitIndex.
this is as per review discussion with [~shashikant] and mukul.
> Add a metric to track the lag between Log commit and Log apply index
> --------------------------------------------------------------------
>
> Key: RATIS-670
> URL: https://issues.apache.org/jira/browse/RATIS-670
> Project: Ratis
> Issue Type: Sub-task
> Components: server
> Reporter: Supratim Deka
> Assignee: Supratim Deka
> Priority: Major
> Attachments: RATIS-670.000.patch, RATIS-670.001.patch
>
>
> The following metric will track by how many entries the log apply index is
> lagging behind the log commit index for the local Ratis log. It should be
> noted that log apply will always lag log commit.
> |logCommitToLogApplyDiff|The difference between lastApplied Index and log
> Commit Index on each of Ratis server. This will give an indication of how the
> stateMachine is behaving with respect to the incoming load.|
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
