[
https://issues.apache.org/jira/browse/YARN-6626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16180010#comment-16180010
]
Jian He commented on YARN-6626:
-------------------------------
Thanks [~eyang] for the patch, some questions and comments on the patch:
- why is ApiServer needed to be extended from WebServices
- why is the change in Resource.java ? If it’s not related to this patch, we
should not include it.
- why is hadoop-yarn-server-common dependency added in api-server pom.xml?
- By default, YARN_API_SERVICES_ENABLE should be false, because the feature is
still experimental
- “yarn.webapp.api-services.enable“: “api-services” can be “api-service” ?
- can you also update the QuickStart.md to metion the option of starting
api-service in embedded mode?
- for the “@XmlType(name)“ annotation, what is the implication of that? Does
this change the filed name of the API ?
> 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,
> 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
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
