[ https://issues.apache.org/jira/browse/YARN-702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13662227#comment-13662227 ]
Siddharth Seth commented on YARN-702: ------------------------------------- When using the MiniCluster, users should be using the configuration object setup by the MiniCluster (This includes the RM address as well), which exposes a method for just this. I don't think this should leak into the NodeManager. > 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