[
https://issues.apache.org/jira/browse/YARN-1940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13974423#comment-13974423
]
Hudson commented on YARN-1940:
------------------------------
SUCCESS: Integrated in Hadoop-trunk-Commit #5537 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/5537/])
YARN-1940. deleteAsUser() terminates early without deleting more files on
error. Contributed by Rushabh S Shah (jlowe:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1588546)
* /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt
*
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/native/container-executor/impl/container-executor.c
> deleteAsUser() terminates early without deleting more files on error
> --------------------------------------------------------------------
>
> Key: YARN-1940
> URL: https://issues.apache.org/jira/browse/YARN-1940
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Kihwal Lee
> Assignee: Rushabh S Shah
> Fix For: 3.0.0, 2.5.0
>
> Attachments: YARN-1940-v2.patch, YARN-1940.patch
>
>
> In container-executor.c, delete_path() returns early when unlink() against a
> file or a symlink fails. We have seen many cases of the error being ENOENT,
> which can safely be ignored during delete.
> This is what we saw recently: An app mistakenly created a large number of
> files in the local directory and the deletion service failed to delete a
> significant portion of them due to this bug. Repeatedly hitting this on the
> same node led to exhaustion of inodes in one of the partitions.
> Beside ignoring ENOENT, delete_path() can simply skip the failed one and
> continue in some cases, rather than aborting and leaving files behind.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
