Return-Path: X-Original-To: apmail-hadoop-mapreduce-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-mapreduce-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id AD56D11521 for ; Thu, 3 Jul 2014 05:33:50 +0000 (UTC) Received: (qmail 66433 invoked by uid 500); 3 Jul 2014 05:33:50 -0000 Delivered-To: apmail-hadoop-mapreduce-issues-archive@hadoop.apache.org Received: (qmail 66377 invoked by uid 500); 3 Jul 2014 05:33:50 -0000 Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: mapreduce-issues@hadoop.apache.org Delivered-To: mailing list mapreduce-issues@hadoop.apache.org Received: (qmail 66364 invoked by uid 99); 3 Jul 2014 05:33:50 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Jul 2014 05:33:50 +0000 Date: Thu, 3 Jul 2014 05:33:50 +0000 (UTC) From: "Karthik Kambatla (JIRA)" To: mapreduce-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (MAPREDUCE-4758) jobhistory web ui not showing correct # failed reducers MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/MAPREDUCE-4758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated MAPREDUCE-4758: ---------------------------------------- Target Version/s: 2.6.0 (was: 3.0.0, 2.5.0) > jobhistory web ui not showing correct # failed reducers > ------------------------------------------------------- > > Key: MAPREDUCE-4758 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-4758 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: jobhistoryserver, webapps > Affects Versions: 0.23.4 > Reporter: Thomas Graves > Priority: Critical > > we had a job fail due to a reducer failing 4 times. Unfortunately the job history UI didn't show this particular failed reducer which lead to confusion as to why the job failed. > This reducer failed to launch all 4 task attempts with a Token Expiration error and the jobhistory file only gets an event when the task attempt transitions to launched. The webapp JobInfo object only counts the task attempts in the jobhistory file to display under the "Attempt Type" table, so since this task didn't have an attempt with it, it did show it on the UI. > We need to reconcile the task list with the task attempts or also shows more stats for the tasks vs task attempts. -- This message was sent by Atlassian JIRA (v6.2#6252)