Steve Loughran commented on YARN-1565:

test failed as HTML came back.

One thing I'd recommend is that if an assert isn't met (e.g. content type, 
status code), the test should try to either print out the HTTP Response text or 
(maybe) include it in the exception test. That way we can debug the failures 
from just the test results

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