hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Enis Soztutar (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-53) MapReduce log files should be storable in dfs.
Date Thu, 25 Oct 2007 15:13:50 GMT

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

Enis Soztutar updated HADOOP-53:
--------------------------------

    Attachment: mapredDFSLog_v2.patch

Patch updated to trunk, FsLogAppender is refactored to o.a.h.util. 

bq. The tasks using FsLogAppender enter a zombie state and wont finalize.
I have failed to reproduce this in several tests running different jobs, i guess the zombie
processes were the leftovers caused by the earlier versions of the patch. 

Can someone review the patch please? 

> MapReduce log files should be storable in dfs.
> ----------------------------------------------
>
>                 Key: HADOOP-53
>                 URL: https://issues.apache.org/jira/browse/HADOOP-53
>             Project: Hadoop
>          Issue Type: New Feature
>          Components: mapred
>    Affects Versions: 0.16.0
>            Reporter: Doug Cutting
>            Assignee: Enis Soztutar
>             Fix For: 0.16.0
>
>         Attachments: mapredDFSLog_v1.patch, mapredDFSLog_v2.patch
>
>
> It should be possible to cause a job's log output to be stored in dfs.  The jobtracker's
log output and (optionally) all tasktracker log output related to a job should be storable
in a job-specified dfs directory.

-- 
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