hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Yang (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-6626) Embed REST API service into RM
Date Tue, 26 Sep 2017 23:17:00 GMT

     [ 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.008.patch

Update api-services to api-service.

> 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
>
>
> 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-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org


Mime
View raw message