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 9E33B200BFF for ; Tue, 17 Jan 2017 20:28:01 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 9D081160B46; Tue, 17 Jan 2017 19:28:01 +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 E5462160B30 for ; Tue, 17 Jan 2017 20:28:00 +0100 (CET) Received: (qmail 96918 invoked by uid 500); 17 Jan 2017 19:28:00 -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 96905 invoked by uid 99); 17 Jan 2017 19:28:00 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Jan 2017 19:28:00 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id AB89618066C for ; Tue, 17 Jan 2017 19:27:59 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -1.199 X-Spam-Level: X-Spam-Status: No, score=-1.199 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-2.999] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id 3KPdogg-ck73 for ; Tue, 17 Jan 2017 19:27:58 +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 8210A5FB5B for ; Tue, 17 Jan 2017 19:27:58 +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 C9D86E7373 for ; Tue, 17 Jan 2017 19:27:27 +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 9E2BC25287 for ; Tue, 17 Jan 2017 19:27:26 +0000 (UTC) Date: Tue, 17 Jan 2017 19:27:26 +0000 (UTC) From: "Joep Rottinghuis (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-6095) create a REST API that returns the clusters for a given app id MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 17 Jan 2017 19:28:01 -0000 [ https://issues.apache.org/jira/browse/YARN-6095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15826652#comment-15826652 ] Joep Rottinghuis commented on YARN-6095: ---------------------------------------- Just to make sure we capture part of the discussion at the end of YARN-5378: For a cloud environment, clusters may be ephemeral and come and go relatively quickly. For that use-case it is desirable to enumerate clusters. I think that is still a little different than this specific jira, which would take an app ID and return the list of clusters that this app ID occurred on. Note that in the vast majority of cases this would return only 1 cluster (or none I suppose). The use-case of enumerating clusters should use useful without _any_ arguments. That can happen in two ways: either strongly write this for every app, which means that we keep inserting / overwriting, or process this after the fact in the back-end. In either case, that should be a separate jira from this one imho, unless I mis-understood the discussion on YARN-5378. cc [~rohithsharma] [~varun_saxena] [~sunilg] > create a REST API that returns the clusters for a given app id > -------------------------------------------------------------- > > Key: YARN-6095 > URL: https://issues.apache.org/jira/browse/YARN-6095 > Project: Hadoop YARN > Issue Type: Sub-task > Components: timelineserver > Reporter: Sangjin Lee > > It would be good to have a timeline service REST endpoint that can return the list of clusters for a given app id. This becomes possible after YARN-5378 is in. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: yarn-issues-help@hadoop.apache.org