Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Mon, 21 Jul 2014 18:12:40 +0000 (UTC)
From: "Colin Patrick McCabe (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12725957.1404804955388.11165.1405966360512@arcas>
In-Reply-To: <JIRA.12725957.1404804955388@arcas>
References: <JIRA.12725957.1404804955388@arcas>
Subject: [jira] [Moved] (YARN-2327) A hadoop cluster needs clock
 synchronization
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/YARN-2327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Colin Patrick McCabe moved HADOOP-10794 to YARN-2327:
-----------------------------------------------------

        Key: YARN-2327  (was: HADOOP-10794)
    Project: Hadoop YARN  (was: Hadoop Common)

> A hadoop cluster needs clock synchronization
> --------------------------------------------
>
>                 Key: YARN-2327
>                 URL: https://issues.apache.org/jira/browse/YARN-2327
>             Project: Hadoop YARN
>          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)