[
https://issues.apache.org/jira/browse/HDDS-1783?focusedWorklogId=302983&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-302983
]
ASF GitHub Bot logged work on HDDS-1783:
----------------------------------------
Author: ASF GitHub Bot
Created on: 28/Aug/19 15:54
Start Date: 28/Aug/19 15:54
Worklog Time Spent: 10m
Work Description: avijayanhwx commented on pull request #1363: HDDS-1783
: Latency metric for applyTransaction in ContainerStateMach…
URL: https://github.com/apache/hadoop/pull/1363#discussion_r318661205
##########
File path:
hadoop-hdds/container-service/src/main/java/org/apache/hadoop/ozone/container/common/transport/server/ratis/CSMMetrics.java
##########
@@ -181,6 +183,11 @@ public long getNumBytesCommittedCount() {
return numBytesCommittedCount.value();
}
+ @VisibleForTesting
+ public MutableRate getApplyTransactionLatency() {
Review comment:
Thanks @adoroszlai . I will remove the annotation, and keep the API since we
may use it in the future.
----------------------------------------------------------------
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:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 302983)
Time Spent: 1h 20m (was: 1h 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: 1h 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: [email protected]
For additional commands, e-mail: [email protected]
