hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gera Shegalov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-5754) Preserve Job diagnostics in history
Date Tue, 25 Feb 2014 10:20:21 GMT

     [ 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.v03.patch

Addressing Jason's review:
- dropped default from the Avro file because JHS does not actually use separate reader/writer
schema support in EventReader
- added explicit test for an older version of history file generated with 2.3.0-rc0.
- moved the constant to JobImpl

> 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, MAPREDUCE-5754.v02.patch, MAPREDUCE-5754.v03.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

View raw message