You are viewing a plain text version of this content. The canonical link for it is here.

Posted to mapreduce-issues@hadoop.apache.org by "Gera Shegalov (JIRA)" <ji...@apache.org> on 2014/02/12 05:55:20 UTC

[jira] [Updated] (MAPREDUCE-5754) Preserve Job diagnostics in history

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

Gera Shegalov updated MAPREDUCE-5754:
-------------------------------------

    Attachment: MAPREDUCE-5754.v01.patch

Patch for review

> 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
>         Attachments: MAPREDUCE-5754.v01.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)