[
https://issues.apache.org/jira/browse/HDDS-1783?focusedWorklogId=302707&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-302707
]
ASF GitHub Bot logged work on HDDS-1783:
----------------------------------------
Author: ASF GitHub Bot
Created on: 28/Aug/19 09:27
Start Date: 28/Aug/19 09:27
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-525662020
Thanks @avijayanhwx for working on this. The changes look good. Inn
applyTransaction, we execute different cmds which will vary with latency. For
example, for a write chunk commit, its a rename operation but for putBlock , it
is Rocks DB operation and for close container, its again a disk sync operation
of container state. Depending upon the operation the latency will vary as well.
Can we have per cmd latency metric?
----------------------------------------------------------------
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: 302707)
Time Spent: 0.5h (was: 20m)
> 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: 0.5h
> 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
