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

Haibo Chen updated YARN-5765:
-----------------------------
    Description: 
LinuxContainerExecutor creates usercache/\{userId\}/appcache/\{appId\} with 
wrong group owner, causing Log aggregation and ShuffleHandler to fail because 
node manager process does not have permission to read the files under the 
directory.
This can be easily reproduced by enabling LCE and submitting a MR example job 
as a user that does not belong to the same group that NM process belongs to. 

  was:
LinuxContainerExecutor creates usercache/\{userId\}/appcache/\{appId\} with 
wrong group owner, causing Log aggregation and ShuffleHandler to fail because 
node manager process does not have permission to read the files under the 
directory.
This can be easily reproduced by enabling LCE and submitting a MR example job. 


> LinuxContainerExecutor creates appcache and its subdirectories with wrong 
> group owner.
> --------------------------------------------------------------------------------------
>
>                 Key: YARN-5765
>                 URL: https://issues.apache.org/jira/browse/YARN-5765
>             Project: Hadoop YARN
>          Issue Type: Bug
>    Affects Versions: 2.8.0, 3.0.0-alpha1
>            Reporter: Haibo Chen
>            Assignee: Naganarasimha G R
>            Priority: Blocker
>
> LinuxContainerExecutor creates usercache/\{userId\}/appcache/\{appId\} with 
> wrong group owner, causing Log aggregation and ShuffleHandler to fail because 
> node manager process does not have permission to read the files under the 
> directory.
> This can be easily reproduced by enabling LCE and submitting a MR example job 
> as a user that does not belong to the same group that NM process belongs to. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to