You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-issues@hadoop.apache.org by "Thomas Graves (JIRA)" <ji...@apache.org> on 2012/08/31 20:59:07 UTC

[jira] [Updated] (YARN-66) aggregated logs permissions not set properly

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

Thomas Graves updated YARN-66:
------------------------------

    Attachment: YARN-66.patch

Set the umask before creating the file to give make it group readable
                
> 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
>         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