[
https://issues.apache.org/jira/browse/HDFS-6236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13967658#comment-13967658
]
Hudson commented on HDFS-6236:
------------------------------
SUCCESS: Integrated in Hadoop-trunk-Commit #5509 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/5509/])
HDFS-6236. ImageServlet should use Time#monotonicNow to measure latency.
Contributed by Chris Nauroth. (cnauroth:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1586902)
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/ImageServlet.java
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestCheckpoint.java
> ImageServlet should use Time#monotonicNow to measure latency.
> -------------------------------------------------------------
>
> Key: HDFS-6236
> URL: https://issues.apache.org/jira/browse/HDFS-6236
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Affects Versions: 3.0.0, 2.4.0
> Reporter: Chris Nauroth
> Assignee: Chris Nauroth
> Priority: Minor
> Attachments: HDFS-6236.1.patch
>
>
> {{ImageServlet}} currently uses {{Time#now}} to get file transfer latency
> measurements and pass them to the metrics system. It would be preferrable to
> use {{Time#monotonicNow}} so that we're using the most precise available
> system timer, and we're not subject to odd bugs that could result in negative
> latency measurements, like resetting the system clock.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
