[ https://issues.apache.org/jira/browse/YARN-1565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14048704#comment-14048704 ]
Steve Loughran commented on YARN-1565: -------------------------------------- I think this should be part of the REST API -we just publish some JSON that provides this information to local and remote systems # the values listed above # all the special expanded variables you can use in command creation # a select subset of YARN/Hadoop properties:defaultFS, yarn.vmem, & some other props we think are useful for clients and debugging. We shouldn't publish the whole aggregate -site.xml values as that can leak private keys to object stores. > Add a way for YARN clients to get critical YARN system properties from the RM > ----------------------------------------------------------------------------- > > Key: YARN-1565 > URL: https://issues.apache.org/jira/browse/YARN-1565 > Project: Hadoop YARN > Issue Type: Improvement > Components: resourcemanager > Affects Versions: 2.2.0 > Reporter: Steve Loughran > > If you are trying to build up an AM request, you need to know > # the limits of memory, core &c for the chosen queue > # the existing YARN classpath > # the path separator for the target platform (so your classpath comes out > right) > # cluster OS: in case you need some OS-specific changes > The classpath can be in yarn-site.xml, but a remote client may not have that. > The site-xml file doesn't list Queue resource limits, cluster OS or the path > separator. > A way to query the RM for these values would make it easier for YARN clients > to build up AM submissions with less guesswork and client-side config. -- This message was sent by Atlassian JIRA (v6.2#6252)