You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Erik Krogen (JIRA)" <ji...@apache.org> on 2017/04/04 15:44:41 UTC
[jira] [Updated] (HDFS-11615) FSNamesystemLock metrics can be
inaccurate due to millisecond precision
[ https://issues.apache.org/jira/browse/HDFS-11615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Erik Krogen updated HDFS-11615:
-------------------------------
Summary: FSNamesystemLock metrics can be inaccurate due to millisecond precision (was: FSNamesystemLock metrics can be inaccurate due millisecond precision)
> 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
>
> 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: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org