Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Tue, 26 May 2015 21:50:21 +0000 (UTC)
From: "Chris Nauroth (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12828998.1431385969000.32355.1432677021535@Atlassian.JIRA>
In-Reply-To: <JIRA.12828998.1431385969000@Atlassian.JIRA>
References: <JIRA.12828998.1431385969000@Atlassian.JIRA>
 <JIRA.12828998.1431385969063@arcas>
Subject: [jira] [Commented] (YARN-3626) On Windows localized resources are
 not moved to the front of the classpath when they should be
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Chris Nauroth commented on YARN-3626:
-------------------------------------

Thanks, Craig!  We could potentially stick the {{@Private}} annotation directly onto {{ApplicationConstants#CLASSPATH_PREPEND_DISTCACHE}}.  I'll let Vinod chime in on whether or not this was the intent of his feedback.

+1 from me, pending Jenkins run.

> On Windows localized resources are not moved to the front of the classpath when they should be
> ----------------------------------------------------------------------------------------------
>
>                 Key: YARN-3626
>                 URL: https://issues.apache.org/jira/browse/YARN-3626
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: yarn
>         Environment: Windows
>            Reporter: Craig Welch
>            Assignee: Craig Welch
>             Fix For: 2.7.1
>
>         Attachments: YARN-3626.0.patch, YARN-3626.11.patch, YARN-3626.14.patch, YARN-3626.15.patch, YARN-3626.4.patch, YARN-3626.6.patch, YARN-3626.9.patch
>
>
> In response to the mapreduce.job.user.classpath.first setting the classpath is ordered differently so that localized resources will appear before system classpath resources when tasks execute.  On Windows this does not work because the localized resources are not linked into their final location when the classpath jar is created.  To compensate for that localized jar resources are added directly to the classpath generated for the jar rather than being discovered from the localized directories.  Unfortunately, they are always appended to the classpath, and so are never preferred over system resources.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)