[
https://issues.apache.org/jira/browse/RATIS-670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16928159#comment-16928159
]
Shashikant Banerjee edited comment on RATIS-670 at 9/12/19 3:17 AM:
--------------------------------------------------------------------
Thanks [~sdeka] for updating the patch. StateMachineUpdater increments the
applied index as soon as the call to applyLogToStateMachine happens, but
doesn't wait for the transactions to complete unless it needs to take a
snapshot.. Would it make more sense to update the applied index in the metrics
by fetching it from StateMachine rather that what is maintained in
StateMachineUpdater?
Also, in the test , what we can do is to create a raft cluster and send across
some requests and see if the applied index metrics is getting incremented?
was (Author: shashikant):
Thanks [~sdeka] for updating the patch. StateMachineUpdater increments the
applied index as soon as the call to applyLogToStateMachine happens, but
doesn't wait for the transactions to complete unless it needs to take a
snapshot.. Would it make more sense to update the applied index in the metrics
by fetching it from StateMachine rather that what is maintained in
StateMachineUpdater?
> 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
>
>
> 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)
