[
https://issues.apache.org/jira/browse/YARN-2251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14052369#comment-14052369
]
Hudson commented on YARN-2251:
------------------------------
SUCCESS: Integrated in Hadoop-trunk-Commit #5826 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/5826/])
YARN-2251. Avoid negative elapsed time in JHS/MRAM web UI and services
(Contributed by Zhijie Shen) (junping_du:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1607833)
* /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt
*
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/util/Times.java
*
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/test/java/org/apache/hadoop/yarn/util/TestTimes.java
> Avoid negative elapsed time in JHS/MRAM web UI and services
> -----------------------------------------------------------
>
> Key: YARN-2251
> URL: https://issues.apache.org/jira/browse/YARN-2251
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Zhijie Shen
> Assignee: Zhijie Shen
> Fix For: 2.6.0
>
> Attachments: MAPREDUCE-5940.1.patch, MAPREDUCE-5940.2.patch
>
>
> Recently we observed a rare bug that an elapsed time of a reducer is going to
> be negative on JHS web UI and via REST APIs. While the real reason for this
> bug seems to be clock asynchronization on different hosts, the web frontend
> should have masked the negative values. However, in the current code,
> *org.apache.hadoop.mapreduce.v2.app.webapp.dao.** only check whether the
> elapsed time is -1 or not.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
