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 64D47200D0A for ; Wed, 20 Sep 2017 06:28:06 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 630441609E0; Wed, 20 Sep 2017 04:28:06 +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 A8FD61609DD for ; Wed, 20 Sep 2017 06:28:05 +0200 (CEST) Received: (qmail 33541 invoked by uid 500); 20 Sep 2017 04:28:04 -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 33528 invoked by uid 99); 20 Sep 2017 04:28:04 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Sep 2017 04:28:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id F20C41A609D for ; Wed, 20 Sep 2017 04:28:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-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-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id DyUx8yKcsSFv for ; Wed, 20 Sep 2017 04:28:03 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id EA49A5FCF4 for ; Wed, 20 Sep 2017 04:28:02 +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 5A7C7E0E36 for ; Wed, 20 Sep 2017 04:28:01 +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 4F21F24509 for ; Wed, 20 Sep 2017 04:28:00 +0000 (UTC) Date: Wed, 20 Sep 2017 04:28:00 +0000 (UTC) From: "Jian He (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-7215) REST API to list all deployed services by the same user MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 20 Sep 2017 04:28:06 -0000 [ https://issues.apache.org/jira/browse/YARN-7215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16172724#comment-16172724 ] Jian He commented on YARN-7215: ------------------------------- I didn't mean to make RM store the app configs.... in fact, RM has even no way to get the app configs, yarn-service is just an app to RM's point of view. RM can only store the metaData of YARN. Isn't this jira, by description, to implement "slider list" ? that is as simple as get the list of apps with some meta status info, which "yarn application -list" command already does today. I don't think we need a solr backend to support such simple use-case. That is also how "slider list" worked before... User should be able to simply list services without solr in the picture, just similar to listing apps. I guess you meant bigger things in YARN-7129 to index apps by configs with solr or something? If this jira is meant to implement bigger things in YARN-7129, I can probably open a separate jira to implement "yarn service list" command, which is a fairly simple patch > REST API to list all deployed services by the same user > ------------------------------------------------------- > > Key: YARN-7215 > URL: https://issues.apache.org/jira/browse/YARN-7215 > Project: Hadoop YARN > Issue Type: Sub-task > Components: api, applications > Reporter: Eric Yang > Assignee: Eric Yang > > In Slider, it is possible to list deployed applications from the same user by using: > {code} > slider list > {code} > This API can help UI to display application and services deployed by the same user. > Apiserver does not have ability to list all applications/services at this time. This API requires fast response to list all applications because it is a common UI operation. ApiServer deployed applications persist configuration in HDFS similar to slider, but using directory listing to display deployed application might cost too much overhead to namenode. We may want to use alternative storage mechanism to cache deployed application configuration to accelerate the response time of list deployed applications. -- 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