hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lohit Vijayarenu (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-5529) Task Error messages might not make it to job's history file
Date Wed, 18 Mar 2009 19:01:52 GMT

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

Lohit Vijayarenu updated HADOOP-5529:
-------------------------------------

    Attachment: HADOOP-5529.patch

New status object is replaced in map. This quick patch copies over diagnostic message seen
earlier to new status object so that it is carried forward and hence make it to history file.
Tested this manually by killing jobs at random and see message being copied and logged into
history file.

> Task Error messages might not make it to job's history file
> -----------------------------------------------------------
>
>                 Key: HADOOP-5529
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5529
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.15.3
>            Reporter: Lohit Vijayarenu
>            Priority: Minor
>         Attachments: HADOOP-5529.patch
>
>
> In some cases, Task diagnostic message are received out of order of the actual failed
report. In such cases, loging of failed task to history file might skip logging the previously
received diagnostic message and thus end up with empty message.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message