[ 
https://issues.apache.org/jira/browse/HDDS-1783?focusedWorklogId=303062&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-303062
 ]

ASF GitHub Bot logged work on HDDS-1783:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 28/Aug/19 17:24
            Start Date: 28/Aug/19 17:24
    Worklog Time Spent: 10m 
      Work Description: bshashikant commented on issue #1363: HDDS-1783 : 
Latency metric for applyTransaction in ContainerStateMach…
URL: https://github.com/apache/hadoop/pull/1363#issuecomment-525841965
 
 
   Thanks @avijayanhwx . Yes, the per op applyTransaction latency metrics is 
already there but we don't have writeStateMachineData latency metric which 
again runs in a different executor. Can we add that as well. This can be done 
as a separate jira as well.
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 303062)
    Time Spent: 2h 20m  (was: 2h 10m)

> Latency metric for applyTransaction in ContainerStateMachine
> ------------------------------------------------------------
>
>                 Key: HDDS-1783
>                 URL: https://issues.apache.org/jira/browse/HDDS-1783
>             Project: Hadoop Distributed Data Store
>          Issue Type: Improvement
>          Components: Ozone Datanode
>            Reporter: Supratim Deka
>            Assignee: Aravindan Vijayan
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 2h 20m
>  Remaining Estimate: 0h
>
> applyTransaction is invoked from the Ratis pipeline and the 
> ContainerStateMachine
> uses a async executor to complete the task.
>  
> We require a latency metric to track the performance of log apply operations 
> in the state machine. This will measure the end-to-end latency of apply which 
> includes the queueing delay in the executor queues. Combined with the latency 
> measurement in HddsDispatcher, this will be an indicator if the executors are 
> overloaded.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org

Reply via email to