[
https://issues.apache.org/jira/browse/YARN-6626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Yang updated YARN-6626:
----------------------------
Attachment: YARN-6626.yarn-native-services.001.patch
First draft for bundle api service REST API in RM. This JIRA depends on
pom.xml file modification in YARN-7193.
The current approach is to bundle the REST API code as a jar file, and allow
hadoop-yarn-ui project to bundle the REST API jar file, and configure web.xml
to load REST API classes.
The drawback of this approach is the URI is prefixed with /ui2 instead of
/ws/v1/. /ws/v1/ is already taken by resource manager's own REST API. We
probably want to label this as /ws/v2/ or /app/v1/ as prefix of REST API to
avoid confusion between resource manager API vs application REST API.
The alternative method is to move the code from ApiServer.java into
RMWebApp.java, which makes that file bloated, and can't be separated as another
standalone server.
> Embed REST API service into RM
> ------------------------------
>
> Key: YARN-6626
> URL: https://issues.apache.org/jira/browse/YARN-6626
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Gour Saha
> Fix For: yarn-native-services
>
> Attachments: YARN-6626.yarn-native-services.001.patch
>
>
> As of now the deployment model of the Native Services REST API service is
> standalone. There are several cross-cutting solutions that can be inherited
> for free (kerberos, HA, ACLs, trusted proxy support, etc.) by the REST API
> service if it is embedded into the RM process. In fact we can expose the REST
> API via the same port as RM UI (8088 default). The URI path
> /services/v1/applications will distinguish the REST API calls from other RM
> APIs.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
