[
https://issues.apache.org/jira/browse/RATIS-670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16928212#comment-16928212
]
Supratim Deka commented on RATIS-670:
-------------------------------------
Thanks for the review [~shashikant]
In patch 002, I have added another metric gauge to track the applied index
reported by the statemachine.
Now we can track both the markers separately - applied index from Ratis/SM
Updater and applied index from the SM.
Regarding the test case. please suggest an existing cluster based test where we
can ensure applied index moves up in a reliable manner, I will go ahead and add
the new metrics. Otherwise, I hope it is ok to go ahead with the basic test in
the patch which simply checks that the metric can be loaded from the registry.
> Add a metric to track StateMachine 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,
> RATIS-670.002.patch
>
>
> Plotting the Log apply index (log index applied on the StateMachine) against
> the RaftLog commit index, is useful in monitoring the performance of the
> statemachine.
> This jira adds a metric/gauge which tracks the current value of log apply
> index.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
