Steve Loughran commented on YARN-1565:

Looking at the code, given the SystemPropertyInfo is to be a new structure that 
will evolve over time, let's keep it as simple as possible -making the 
classpath field public and skipping the explicit accessor method. 

Otherwise, I like this: Addresses a core problem on hadoop apps. 

I think later on I'd like more of the environment and things, but starting with 
classpath means we don't have to worry about exposing security information 
which we could otherwise unintentionally leak. (other than the list of 
artifacts on the CP,  hence potentially known vulnerabilities). 

Now, we'll also need some documentation in the yarn-site pages, won't we?

> 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
>         Attachments: YARN-1565-001.patch, YARN-1565-002.patch, 
> YARN-1565-003.patch
> 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

Reply via email to