Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Fri, 1 Apr 2011 18:43:05 +0000 (UTC)
From: "Todd Lipcon (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: 
 <1408120496.29268.1301683385731.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1394105473.29248.1301683145856.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (MAPREDUCE-2418) Errors not shown in the
 JobHistory servlet (specifically Counter Limit Exceeded)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/MAPREDUCE-2418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13014790#comment-13014790 ] 

Todd Lipcon commented on MAPREDUCE-2418:
----------------------------------------

I've noticed a lot of patches going into the 0.20.20x branches recently. Are these not applicable to trunk as well? It seems like this branch is starting to look more like a fork instead of a set of backports.

> Errors not shown in the JobHistory servlet (specifically Counter Limit Exceeded)
> --------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-2418
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2418
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>    Affects Versions: 0.20.203.0, 0.20.203.1
>            Reporter: Siddharth Seth
>            Assignee: Siddharth Seth
>            Priority: Minor
>             Fix For: 0.20.204.0
>
>         Attachments: MR2418.patch
>
>
> Job error details are not displayed in the JobHistory servlet. e.g. Errors like 'Counter limit exceeded for a job'. 
> jobdetails.jsp has 'Failure Info', but this is missing in jobdetailshistory.jsp

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira