hadoop-yarn-issues mailing list archives

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

    [ https://issues.apache.org/jira/browse/YARN-6626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16181755#comment-16181755
] 

Gour Saha commented on YARN-6626:
---------------------------------

bq. Added ability to load ApiServer to RM as a web filter using reflection. This is done to
avoid Maven cyclic dependency on hadoop-yarn-services-api module.
[~eyang], is there any annotation support in Yarn (similar to Spring framework) which can
be applied to the ApiServer class and then at runtime RM scans for all classes (from a specified
list of packages) for such annotations and loads them appropriately? If not, we should at
least add a comment as to why we are doing the reflection (to avoid compile-time cyclic dependency,
etc.) so that if such an annotation framework is created later, it can be incorporated for
ApiServer.

> 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