[
https://issues.apache.org/jira/browse/YARN-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13458761#comment-13458761
]
Jason Lowe commented on YARN-106:
---------------------------------
How will public files in the distributed cache work properly if the local
directory doesn't have world access? We're already locking down access to the
directories within these top-level directories for files that aren't public, so
even if they are left at 755 I'm not sure there is a real need to set them
otherwise. Maybe there's a valid use-case I'm missing?
I agree I'd rather avoid adding yet more configs, especially since it would be
easy to configure a broken setup (e.g.: files put in the public cache but are
inaccessible to many jobs or logs can't be served/aggregated by the
nodemanager).
> Nodemanager needs to set permissions of local directories
> ---------------------------------------------------------
>
> Key: YARN-106
> URL: https://issues.apache.org/jira/browse/YARN-106
> Project: Hadoop YARN
> Issue Type: Bug
> Components: nodemanager
> Affects Versions: 0.23.3, 2.0.0-alpha
> Reporter: Jason Lowe
> Assignee: Jason Lowe
> Attachments: YARN-106.patch
>
>
> If the nodemanager process is running with a restrictive default umask (e.g.:
> 0077) then it will create its local directories with permissions that are too
> restrictive to allow containers from other users to run.
--
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
