[
https://issues.apache.org/jira/browse/YARN-702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13662367#comment-13662367
]
Siddharth Seth commented on YARN-702:
-------------------------------------
I though HBase had already changed their tests to make use of the configuration
returned by the MiniCluster. In the two cases that you saw, were the
applications explicitly picking up the RM address - or was it restricted to the
'isMiniCluster' config variable ?
In terms of being similar to a normal cluster - the cluster configuration which
is used by clients is based on the cluster setup (RM address, jars, etc).
Similarly, when the MiniCluster comes up - it makes it's configuration (which
is dynamic) available via the getConfiguration method.
I'd agree with the bit about having this documented properly. What could also
be done, is make cluster specific configuration (similar to the contents of
yarn-site.xml) available via the MiniCluster.
> 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
