Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Fri, 4 Jul 2014 09:01:41 +0000 (UTC)
From: "Junping Du (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12723562.1403674217709.3854.1404464501641@arcas>
In-Reply-To: <JIRA.12723562.1403674217709@arcas>
References: <JIRA.12723562.1403674217709@arcas>
Subject: [jira] [Moved] (YARN-2251) Avoid negative elapsed time in JHS/MRAM
 web UI and services
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Junping Du moved MAPREDUCE-5940 to YARN-2251:
---------------------------------------------

    Component/s:     (was: webapps)
                     (was: jobhistoryserver)
                     (was: mr-am)
            Key: YARN-2251  (was: MAPREDUCE-5940)
        Project: Hadoop YARN  (was: Hadoop Map/Reduce)

> 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
>         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)