[
https://issues.apache.org/jira/browse/YARN-9442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16811021#comment-16811021
]
Jim Brennan commented on YARN-9442:
-----------------------------------
{quote}
I think the group read permission is used by shuffle handler to access map
output. See MAPREDUCE-3728 for related discussion.
{quote}
[~eyang] thanks for the comment!
This change should not affect shuffle handler because it does not change the
permissions for the map output dir - it only affects the container working
directories, which are peers of the output dir:
{noformat}
ls -l usercache/jbrennan02/appcache/application_1554316092589_0005
drwx--s--- 4 jbrennan02 hadoop 4096 Apr 5 15:03
container_1554316092589_0005_01_000001
drwx--s--- 3 jbrennan02 hadoop 4096 Apr 5 15:03
container_1554316092589_0005_01_000003
drwx--s--- 3 jbrennan02 hadoop 4096 Apr 5 15:03
container_1554316092589_0005_01_000004
drwx--x--- 6 jbrennan02 hadoop 4096 Apr 5 15:03 filecache
drwxr-s--- 4 jbrennan02 hadoop 4096 Apr 5 15:03 output
drwxrwx--- 2 jbrennan02 hadoop 4096 Apr 5 15:03 work
{noformat}
> container working directory has group read permissions
> ------------------------------------------------------
>
> Key: YARN-9442
> URL: https://issues.apache.org/jira/browse/YARN-9442
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: yarn
> Affects Versions: 3.2.2
> Reporter: Jim Brennan
> Assignee: Jim Brennan
> Priority: Minor
> Attachments: YARN-9442.001.patch, YARN-9442.002.patch
>
>
> Container working directories are currently created with permissions 0750,
> owned by the user and with the group set to the node manager group.
> Is there any reason why these directories need group read permissions?
> I have been testing with group read permissions removed and so far I haven't
> encountered any problems.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
