[ 
https://issues.apache.org/jira/browse/YARN-4177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14877134#comment-14877134
 ] 

Steve Loughran commented on YARN-4177:
--------------------------------------

As of this week, i don't trust monotonic clocks on multi-socket servers: 
http://steveloughran.blogspot.co.uk/2015/09/time-on-multi-core-multi-socket-servers.html



> 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 [~ste...@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)

Reply via email to