[
https://issues.apache.org/jira/browse/HADOOP-10794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14064326#comment-14064326
]
eric baldeschwieler commented on HADOOP-10794:
----------------------------------------------
Agreed. Doing math between server clocks is an anti-pattern to be avoided.
We should file JIRAs to fix any instances of that , because the result is
not a usable number given the error bars today.
On Wednesday, July 16, 2014, Colin Patrick McCabe (JIRA) <[email protected]>
--
---
E14 - typing on glass
> A hadoop cluster needs clock synchronization
> --------------------------------------------
>
> Key: HADOOP-10794
> URL: https://issues.apache.org/jira/browse/HADOOP-10794
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Zhijie Shen
>
> As a distributed system, a hadoop cluster wants the clock on all the
> participating hosts synchronized. Otherwise, some problems might happen. For
> example, in YARN-2251, due to the clock on the host for the task container
> falls behind that on the host of the AM container, the computed elapsed time
> (the diff between the timestamps produced on two hosts) becomes negative.
> In YARN-2251, we tried to mask the negative elapsed time. However, we should
> seek for a decent long term solution, such as providing mechanism to do and
> check clock synchronization.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
