hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Lowe (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-1386) NodeManager mistakenly loses resources and relocalizes them
Date Tue, 12 Nov 2013 20:44:18 GMT

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

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

    Attachment: YARN-1386.patch

Bobby helped me clean up some leaked processes on one of the build machines.  Uploading the
same patch to kick Jenkins again.

> 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
>            Assignee: Jason Lowe
>            Priority: Critical
>         Attachments: YARN-1386.patch, YARN-1386.patch
>
>
> 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)

Mime
View raw message