hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sandy Ryza (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-702) minicluster classpath construction requires user to set yarn.is.minicluster in the job conf
Date Mon, 20 May 2013 23:07:15 GMT

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

Sandy Ryza commented on YARN-702:
---------------------------------

In both cases, the applications were setting the RM address by pulling the value from the
MiniCluster config, but not using the config in general.
                
> minicluster classpath construction requires user to set yarn.is.minicluster in the job
conf
> -------------------------------------------------------------------------------------------
>
>                 Key: YARN-702
>                 URL: https://issues.apache.org/jira/browse/YARN-702
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: nodemanager
>    Affects Versions: 2.0.4-alpha
>            Reporter: Sandy Ryza
>            Assignee: Sandy Ryza
>
> YARN-129 improved classpath construction for miniclusters by, when yarn.is.minicluster
is set, adding the current JVM's classpath to the ContainerLaunchContext for the MR AM and
tasks.  An issue with this is that it requires the user to set yarn.is.minicluster on the
mapreduce side in the job conf, if they are not copying to RM conf into the jobconf.
> I think it would be better to bypass the ContainerLaunchContext and instead have the
nodemanager check the property, and if it is true, do the classpath additions there.

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

Mime
View raw message