hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pradeep Subrahmanion (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-1565) Add a way for YARN clients to get critical YARN system properties from the RM
Date Tue, 20 Oct 2015 16:38:27 GMT

     [ https://issues.apache.org/jira/browse/YARN-1565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Pradeep Subrahmanion updated YARN-1565:
---------------------------------------
    Attachment: YARN-1565-001.patch

This patch introduces a new REST API to fetch yarn system properties. Currently only CLASSPATH
is returned through this API but can be extended  to return other YARN system properties that
may be useful for REST clients.

I notice that my patch doesn't address all the points mentioned in this JIRA. But I am submitting
this patch as per last update in YARN-4275.



> 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
(v6.3.4#6332)

Mime
View raw message