Mailing-List: contact yarn-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-dev@hadoop.apache.org
Date: Thu, 11 Oct 2012 17:49:45 +0000 (UTC)
From: "Arun C Murthy (JIRA)" <jira@apache.org>
To: yarn-dev@hadoop.apache.org
Message-ID: <1714974464.30970.1349977785580.JavaMail.jiratomcat@arcas>
Subject: [jira] [Closed] (YARN-66) aggregated logs permissions not set
 properly
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Arun C Murthy closed YARN-66.
-----------------------------

    
> aggregated logs permissions not set properly
> --------------------------------------------
>
>                 Key: YARN-66
>                 URL: https://issues.apache.org/jira/browse/YARN-66
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: nodemanager
>    Affects Versions: 0.23.3
>            Reporter: Thomas Graves
>            Assignee: Thomas Graves
>            Priority: Critical
>             Fix For: 2.0.2-alpha, 0.23.3
>
>         Attachments: YARN-66.patch
>
>
> If the default file permissions are set to something restrictive - like 700, application logs get aggregated and created with those restrictive file permissions which doesn't allow the history server to serve them up.
> They need to be created with group readable similar to how log aggregation sets up the directory permissions.

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