hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1386) NodeManager mistakenly loses resources and relocalizes them
Date Mon, 11 Nov 2013 22:36:18 GMT

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

Hadoop QA commented on YARN-1386:

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 1 new or modified
test files.

    {color:red}-1 javac{color:red}.  The patch appears to cause the build to fail.

Console output: https://builds.apache.org/job/PreCommit-YARN-Build/2418//console

This message is automatically generated.

> 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
> 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

View raw message