hadoop-common-dev mailing list archives

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

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

Owen O'Malley updated HADOOP-53:

    Status: Open  (was: Patch Available)

I think it would be far better to have the FsLogAppender just ignore any messages that came
when the appender wasn't "ready". In particular, we should avoid having special methods that
need to be invoked for initialization and closing. The FsLogAppender should work with non-default
file systems, by doing:

FileSystem fs = path.getFileSystem(conf);
DataOutputStream out = fs.create(path);

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

View raw message