You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Xianyin Xin (JIRA)" <ji...@apache.org> on 2015/09/18 16:33:04 UTC
[jira] [Assigned] (YARN-4177) yarn.util.Clock should not be used to
time a duration or time interval
[ https://issues.apache.org/jira/browse/YARN-4177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Xianyin Xin reassigned YARN-4177:
---------------------------------
Assignee: Xianyin Xin
> yarn.util.Clock should not be used to time a duration or time interval
> ----------------------------------------------------------------------
>
> Key: YARN-4177
> URL: https://issues.apache.org/jira/browse/YARN-4177
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Xianyin Xin
> Assignee: Xianyin Xin
> Attachments: YARN-4177.001.patch, YARN-4177.002.patch
>
>
> There're many places uses Clock to time intervals, which is dangerous as commented by [~stevel@apache.org] in HADOOP-12409. Instead, we should use hadoop.util.Timer#monotonicNow() to get monotonic time. Or we could provide a MonotonicClock in yarn.util considering the consistency of code.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)