hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Lowe (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-5754) Preserve Job diagnostics in history
Date Wed, 26 Feb 2014 21:46:32 GMT

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

Jason Lowe updated MAPREDUCE-5754:
----------------------------------

       Resolution: Fixed
    Fix Version/s: 2.4.0
     Hadoop Flags: Reviewed
           Status: Resolved  (was: Patch Available)

Thanks, Gera!  I committed this to trunk, branch-2, and branch-2.4.

> Preserve Job diagnostics in history
> -----------------------------------
>
>                 Key: MAPREDUCE-5754
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5754
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: jobhistoryserver, mr-am
>    Affects Versions: 2.2.0
>            Reporter: Gera Shegalov
>            Assignee: Gera Shegalov
>             Fix For: 2.4.0
>
>         Attachments: MAPREDUCE-5754.v01.patch, MAPREDUCE-5754.v02.patch, MAPREDUCE-5754.v03.patch,
MAPREDUCE-5754.v04.patch, MAPREDUCE-5754.v05.patch
>
>
> History does not store the runtime diagnostics information. JobHistoryParser tries to
blame a task. We propose to preserve the original runtime diagnostics that covers all the
cases including the job being killed. This is particularly important in the context of user-supplied
diagnostic message as in MAPREDUCE-5648. 



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message