You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Chetna Chaudhari (JIRA)" <ji...@apache.org> on 2017/09/20 03:29:00 UTC
[jira] [Commented] (HADOOP-14713) Audit for durations that should
be measured via Time.monotonicNow
[ https://issues.apache.org/jira/browse/HADOOP-14713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16172672#comment-16172672 ]
Chetna Chaudhari commented on HADOOP-14713:
-------------------------------------------
[~jlowe], [~templedf]: I created few sub-tasks for classes which needs this change. Also, I noticed that, change needs to be done in many test cases. Should I create sub-task per test, or a generic task covering all test cases will be ok? Please advice.
> Audit for durations that should be measured via Time.monotonicNow
> -----------------------------------------------------------------
>
> Key: HADOOP-14713
> URL: https://issues.apache.org/jira/browse/HADOOP-14713
> Project: Hadoop Common
> Issue Type: Improvement
> Reporter: Jason Lowe
> Labels: newbie
>
> Whenever we are measuring a time delta or duration in the same process, the timestamps probably should be using Time.monotonicNow rather than Time.now or System.currentTimeMillis. The latter two are directly reading the system clock which can move faster or slower than actual time if the system is undergoing a time adjustment (e.g.: adjtime or admin sets a new system time).
> We should go through the code base and identify places where the code is using the system clock but really should be using monotonic time.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org