You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Suresh Srinivas (JIRA)" <ji...@apache.org> on 2013/05/25 00:52:24 UTC

[jira] [Updated] (YARN-593) container launch on Windows does not correctly populate classpath with new process's environment variables and localized resources

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

Suresh Srinivas updated YARN-593:
---------------------------------

    Fix Version/s:     (was: 3.0.0)
                   2.0.5-beta

I merged the patch to branch-2.
                
> container launch on Windows does not correctly populate classpath with new process's environment variables and localized resources
> ----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: YARN-593
>                 URL: https://issues.apache.org/jira/browse/YARN-593
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: nodemanager
>    Affects Versions: 3.0.0
>            Reporter: Chris Nauroth
>            Assignee: Chris Nauroth
>             Fix For: 2.0.5-beta
>
>         Attachments: YARN-593.1.patch, YARN-593.2.patch
>
>
> On Windows, we must bundle the classpath of a launched container in an intermediate jar with a manifest.  Currently, this logic incorrectly uses the nodemanager process's environment variables for substitution.  Instead, it needs to use the new environment for the launched process.  Also, the bundled classpath is missing some localized resources for directories, due to a quirk in the way {{File#toURI}} decides whether or not to append a trailing '/'.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira