Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hadoop-dev@lucene.apache.org
Message-ID: <27995705.1193346531598.JavaMail.jira@brutus>
Date: Thu, 25 Oct 2007 14:08:51 -0700 (PDT)
From: "Hadoop QA (JIRA)" <jira@apache.org>
To: hadoop-dev@lucene.apache.org
Subject: [jira] Commented: (HADOOP-53) MapReduce log files should be
 storable in dfs.
In-Reply-To: <13654009.1140640359390.JavaMail.jira@ajax.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Hadoop QA commented on HADOOP-53:
---------------------------------

-1 overall.  Here are the results of testing the latest attachment 
http://issues.apache.org/jira/secure/attachment/12368384/mapredDFSLog_v2.patch
against trunk revision r588341.

    @author +1.  The patch does not contain any @author tags.

    patch -1.  The patch command could not apply the patch.

Console output: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/988/console

This message is automatically generated.

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