[
https://issues.apache.org/jira/browse/YARN-6626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16184332#comment-16184332
]
Hadoop QA commented on YARN-6626:
---------------------------------
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 5s{color}
| {color:red} YARN-6626 does not apply to yarn-native-services. Rebase
required? Wrong Branch? See https://wiki.apache.org/hadoop/HowToContribute for
help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | YARN-6626 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12889514/YARN-6626.yarn-native-services.010.patch
|
| Console output |
https://builds.apache.org/job/PreCommit-YARN-Build/17680/console |
| Powered by | Apache Yetus 0.6.0-SNAPSHOT http://yetus.apache.org |
This message was automatically generated.
> 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
>
>
> 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]
