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

Hudson commented on YARN-7333:
------------------------------

SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #13094 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/13094/])
YARN-7333. container-executor fails to remove entries from a directory 
(nroberts: rev 4540ffd15f1259d99a7847c60d44c51f29faa397)
* (edit) 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/native/container-executor/test/test-container-executor.c
* (edit) 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/native/container-executor/impl/container-executor.c


> container-executor fails to remove entries from a directory that is not 
> writable or executable
> ----------------------------------------------------------------------------------------------
>
>                 Key: YARN-7333
>                 URL: https://issues.apache.org/jira/browse/YARN-7333
>             Project: Hadoop YARN
>          Issue Type: Bug
>    Affects Versions: 2.9.0, 3.0.0-alpha1, 2.8.2
>            Reporter: Jason Lowe
>            Assignee: Jason Lowe
>            Priority: Critical
>             Fix For: 2.9.0, 2.8.2, 2.8.3, 3.0.0
>
>         Attachments: YARN-7333.001.patch, YARN-7333.002.patch
>
>
> Similar to the situation from YARN-4594, container-executor will fail to 
> cleanup directories that do not have write and execute permissions for the 
> directory.  YARN-4594 fixed the scenario where the directory is not readable, 
> but it missed the case where we can open the directory but either not 
> traverse it (i.e.: no execute permission) or cannot remove entries from 
> within it (i.e.: no write permissions).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

Reply via email to