Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 1DECC200D0E for ; Wed, 27 Sep 2017 00:00:08 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 1C5AF1609D7; Tue, 26 Sep 2017 22:00:08 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 61A8D1609C4 for ; Wed, 27 Sep 2017 00:00:07 +0200 (CEST) Received: (qmail 29793 invoked by uid 500); 26 Sep 2017 22:00:06 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 29780 invoked by uid 99); 26 Sep 2017 22:00:06 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Sep 2017 22:00:06 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 15275C85E6 for ; Tue, 26 Sep 2017 22:00:06 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id qRP9AJPGF_f1 for ; Tue, 26 Sep 2017 22:00:05 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id D24BF60D33 for ; Tue, 26 Sep 2017 22:00:04 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id A7E3BE0EF1 for ; Tue, 26 Sep 2017 22:00:03 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 09DAF2427A for ; Tue, 26 Sep 2017 22:00:02 +0000 (UTC) Date: Tue, 26 Sep 2017 22:00:02 +0000 (UTC) From: "Jian He (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-6626) Embed REST API service into RM MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 26 Sep 2017 22:00:08 -0000 [ https://issues.apache.org/jira/browse/YARN-6626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16181652#comment-16181652 ] Jian He commented on YARN-6626: ------------------------------- bq. Every web filter is extended from WebServices. The WebServices is an interface for RM and ATS, it should probably be renamed. I tried to remove this inheritance and it still works. I think we don't need this ? bq. yarn.webapp.api-services.enable call it api-service instead of services? > 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 > > > 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