hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] [Reopened] (YARN-3626) On Windows localized resources are not moved to the front of the classpath when they should be
Date Fri, 15 May 2015 20:50:00 GMT

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

Vinod Kumar Vavilapalli reopened YARN-3626:
-------------------------------------------

As I understand, the current patch doesn't do what you intend. The new configuration added
is supposed to be per app, but it is now a server side configuration. Unless the app and server
share configurations, this should not work.

Reopening this. I think we should revert it (/cc [~xgong]) and continue discussion/work to
do it the right away.

We may have to depend on some sort of a named environment variable or something, assuming
adding a new field in CLC is not desirable.

> 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.4.patch, YARN-3626.6.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)

Mime
View raw message