Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Wed, 29 Aug 2012 05:51:08 +1100 (NCT)
From: "Todd Lipcon (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: <338377499.7765.1346179868685.JavaMail.jiratomcat@arcas>
In-Reply-To: <1678007923.38086.1345597717965.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (MAPREDUCE-4572) Can not access user logs -
 Jetty is not configured by default to serve aliases/symlinks
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/MAPREDUCE-4572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443381#comment-13443381 ] 

Todd Lipcon commented on MAPREDUCE-4572:
----------------------------------------

Also, the description here talks about the Task Log servlet, but the patch itself changes the /logs servlet, which isn't used for fetching task logs.

It may be that this isn't problematic since the /logs servlet is already restricted to only admin-authorized users, but it still makes me somewhat nervous. So we should discuss.
                
> Can not access user logs - Jetty is not configured by default to serve aliases/symlinks
> ---------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-4572
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4572
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: tasktracker, webapps
>    Affects Versions: 1.0.0
>            Reporter: Ahmed Radwan
>            Assignee: Ahmed Radwan
>             Fix For: 1.2.0, 2.2.0-alpha
>
>         Attachments: MAPREDUCE-4572.patch, MAPREDUCE-4572_trunk.patch
>
>
> The task log servlet can no longer access user logs because MAPREDUCE-2415 introduce symlinks to the logs and jetty is not configured by default to serve symlinks. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira