[
https://issues.apache.org/jira/browse/HDFS-11615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15966751#comment-15966751
]
Erik Krogen commented on HDFS-11615:
------------------------------------
I would have suggested just adding an optional time unit parameter which would
allow you to specify that a rate is e.g. measured in nanos to be output as
"AvgTimeNanos"/"NumOps" but leave things as "AvgTime"/"NumOps" by default if no
unit is specified. I see your point about automated tooling, though.
"XxxNanosAvgTime" is reasonable but I'm hesitant to emit a metric called
"XxxNanosNumOps"...
> FSNamesystemLock metrics can be inaccurate due to millisecond precision
> -----------------------------------------------------------------------
>
> Key: HDFS-11615
> URL: https://issues.apache.org/jira/browse/HDFS-11615
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: hdfs
> Affects Versions: 2.7.4
> Reporter: Erik Krogen
> Assignee: Erik Krogen
> Attachments: HDFS-11615.000.patch
>
>
> Currently the {{FSNamesystemLock}} metrics created in HDFS-10872 track the
> lock hold time using {{Timer.monotonicNow()}}, which has millisecond-level
> precision. However, many of these operations hold the lock for less than a
> millisecond, making these metrics inaccurate. We should instead use
> {{System.nanoTime()}} for higher accuracy.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
