Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Sat, 2 Nov 2013 04:21:20 +0000 (UTC)
From: "Jason Lowe (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12677197.1383366020797.9999.1383366080539@arcas>
In-Reply-To: <JIRA.12677197.1383366020797@arcas>
References: <JIRA.12677197.1383366020797@arcas>
Subject: [jira] [Created] (YARN-1386) NodeManager mistakenly loses resources
 and relocalizes them
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Jason Lowe created YARN-1386:
--------------------------------

             Summary: 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: 2.2.0, 0.23.10
            Reporter: Jason Lowe
            Priority: Blocker


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)