hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Lowe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-14713) Audit for durations that should be measured via Time.monotonicNow
Date Tue, 01 Aug 2017 18:20:00 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-14713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16109453#comment-16109453

Jason Lowe commented on HADOOP-14713:

This arose from discussion in HADOOP-14669.  If there ends up being a lot of places that need
to be fixed then this can serve as an umbrella ticket for the subtasks.

> 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
> 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

To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org

View raw message