You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-dev@hadoop.apache.org by "Jian He (JIRA)" <ji...@apache.org> on 2017/10/05 17:56:01 UTC
[jira] [Resolved] (YARN-6626) Embed REST API service into RM
[ https://issues.apache.org/jira/browse/YARN-6626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jian He resolved YARN-6626.
---------------------------
Resolution: Fixed
[~eyang] mentioned a fix in YARN-7202 that fixed this.
I included the fix and tested it worked after the fix
I re-commit this patch with that fix.
> 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
> Assignee: Eric Yang
> Fix For: yarn-native-services
>
> Attachments: YARN-6626.yarn-native-services.001.patch, YARN-6626.yarn-native-services.002.patch, YARN-6626.yarn-native-services.003.patch, YARN-6626.yarn-native-services.004.patch, YARN-6626.yarn-native-services.005.patch, YARN-6626.yarn-native-services.006.patch, YARN-6626.yarn-native-services.007.patch, YARN-6626.yarn-native-services.008.patch, YARN-6626.yarn-native-services.009.patch, YARN-6626.yarn-native-services.010.patch, YARN-6626.yarn-native-services.011.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-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-dev-help@hadoop.apache.org