hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-66) aggregated logs permissions not set properly
Date Fri, 31 Aug 2012 19:57:07 GMT

    [ https://issues.apache.org/jira/browse/YARN-66?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13446302#comment-13446302

Hadoop QA commented on YARN-66:

+1 overall.  Here are the results of testing the latest attachment 
  against trunk revision .

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

    +1 tests included.  The patch appears to include 1 new or modified test files.

    +1 javac.  The applied patch does not increase the total number of javac compiler warnings.

    +1 javadoc.  The javadoc tool did not generate any warning messages.

    +1 eclipse:eclipse.  The patch built with eclipse:eclipse.

    +1 findbugs.  The patch does not introduce any new Findbugs (version 1.3.9) warnings.

    +1 release audit.  The applied patch does not increase the total number of release audit

    +1 core tests.  The patch passed unit tests in hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common.

    +1 contrib tests.  The patch passed contrib unit tests.

Test results: https://builds.apache.org/job/PreCommit-YARN-Build/13//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/13//console

This message is automatically generated.
> 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

View raw message