hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Siddharth Seth (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-4693) Historyserver should provide counters for failed tasks
Date Wed, 27 Feb 2013 20:59:13 GMT

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

Siddharth Seth commented on MAPREDUCE-4693:

The latest patch (MAPREDUCE-4693.4.patch) looks good. +1 
There's a couple of follow up tasks which may be required though. Job level counters in case
of job failure. Task.selectBestAttempt needs a fix.
> Historyserver should provide counters for failed tasks
> ------------------------------------------------------
>                 Key: MAPREDUCE-4693
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4693
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: jobhistoryserver, mrv2
>    Affects Versions: 2.0.3-alpha, 0.23.6
>            Reporter: Jason Lowe
>            Assignee: Xuan Gong
>              Labels: usability
>         Attachments: job_1361915610508_0012-1361920250120-xuan-random-writer-1361920333343-9-0-FAILED-default.jhist,
MAPREDUCE-4693.1.patch, MAPREDUCE-4693.2.patch, MAPREDUCE-4693.3.patch, MAPREDUCE-4693.4.patch
> Currently the historyserver is not providing counters for failed tasks, even though they
are available via the AM as long as the job is still running.  Those counters are lost when
the client needs to redirect to the historyserver after the job completes.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message