Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Sat, 22 Oct 2011 05:00:32 +0000 (UTC)
From: "Siddharth Seth (Updated) (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: 
 <1357120083.4305.1319259632774.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1711201941.19590.1315866308873.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (MAPREDUCE-2989) JobHistory should link to task
 logs
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Siddharth Seth updated MAPREDUCE-2989:
--------------------------------------

    Attachment: MR2989_v1.txt

Adds a log servlet running on the history server - which reads the aggregated logs from hdfs.
Changed the log format to include owner and ACL information. This needs some more change to be able to access individual log types more easily, and other improvements - will open a separate jira for that.
The patch does not enable LogAggregation (will enable it after MR3146) - can be enabled via {{LogAggregationService.handle}} and TestLogAggregationService @Ignore.

Tested with aggregation enabled on a secure and non-secure cluster.
                
> JobHistory should link to task logs
> -----------------------------------
>
>                 Key: MAPREDUCE-2989
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2989
>             Project: Hadoop Map/Reduce
>          Issue Type: Sub-task
>          Components: mrv2
>    Affects Versions: 0.23.0, 0.24.0
>            Reporter: Siddharth Seth
>            Assignee: Siddharth Seth
>            Priority: Critical
>             Fix For: 0.23.0
>
>         Attachments: MR2989_v1.txt
>
>
> The log link on the task attempt page is currently broken - since it relies on a ContainerId. We should either pass the containerId via a history event - or some kind of field with information about the log location.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira