You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-issues@hadoop.apache.org by "Jason Lowe (JIRA)" <ji...@apache.org> on 2013/11/02 07:09:17 UTC

[jira] [Updated] (YARN-1386) NodeManager mistakenly loses resources and relocalizes them

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

Jason Lowe updated YARN-1386:
-----------------------------

    Priority: Critical  (was: Blocker)

This is a problem when the cluster is configured with a restrictive umask (e.g.: fs.permissions.umask-mode=0077).

> NodeManager mistakenly loses resources and relocalizes them
> -----------------------------------------------------------
>
>                 Key: YARN-1386
>                 URL: https://issues.apache.org/jira/browse/YARN-1386
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: nodemanager
>    Affects Versions: 0.23.10, 2.2.0
>            Reporter: Jason Lowe
>            Priority: Critical
>
> When a local resource that should already be present is requested again, the nodemanager checks to see if it still present.  However the method it uses to check for presence is via File.exists() as the user of the nodemanager process. If the resource was a private resource localized for another user, it will be localized to a location that is not accessible by the nodemanager user.  Therefore File.exists() returns false, the nodemanager mistakenly believes the resource is no longer available, and it proceeds to localize it over and over.



--
This message was sent by Atlassian JIRA
(v6.1#6144)