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 37434200CEE for ; Mon, 7 Aug 2017 20:27:09 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 35F54165CE7; Mon, 7 Aug 2017 18:27:09 +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 79FA6165CE8 for ; Mon, 7 Aug 2017 20:27:08 +0200 (CEST) Received: (qmail 52543 invoked by uid 500); 7 Aug 2017 18:27:07 -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 52413 invoked by uid 99); 7 Aug 2017 18:27:07 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 07 Aug 2017 18:27:07 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id D6359C05DA for ; Mon, 7 Aug 2017 18:27:06 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, 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 (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id 73-vJ2sKcSLG for ; Mon, 7 Aug 2017 18:27:02 +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 1C0855F6D2 for ; Mon, 7 Aug 2017 18:27: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 5F2B8E0630 for ; Mon, 7 Aug 2017 18:27: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 7ED2224181 for ; Mon, 7 Aug 2017 18:27:00 +0000 (UTC) Date: Mon, 7 Aug 2017 18:27:00 +0000 (UTC) From: "Grant Sohn (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-6894) RM Apps API returns only active apps when query parameter queue used MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 07 Aug 2017 18:27:09 -0000 [ https://issues.apache.org/jira/browse/YARN-6894?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D16116= 992#comment-16116992 ]=20 Grant Sohn commented on YARN-6894: ---------------------------------- I think this is too subtle. I would say: {noformat} queue - queue name, **Note** specifying the queue parameter will implicitl= y filter on only the **unfinished** applications that are currently in this= queue {noformat} Since it's not standard, it really needs to be called out more clearly. Ho= wever, I on > RM Apps API returns only active apps when query parameter queue used > -------------------------------------------------------------------- > > Key: YARN-6894 > URL: https://issues.apache.org/jira/browse/YARN-6894 > Project: Hadoop YARN > Issue Type: Bug > Components: resourcemanager, restapi > Reporter: Grant Sohn > Assignee: Gergely Nov=C3=A1k > Priority: Minor > Attachments: YARN-6894.001.patch > > > If you run RM's Cluster Applications API with no query parameters, you ge= t a list of apps. > If you run RM's Cluster Applications API with any query parameters other = than "queue" you get the list of apps with the parameter filters being appl= ied. > However, when you use the "queue" query parameter, you only see the appli= cations that are active in the cluster (NEW, NEW_SAVING, SUBMITTED, ACCEPTE= D, RUNNING). This behavior is inconsistent with the API. If there is a so= und reason behind this, it should be documented and it seems like there mig= ht be as the mapred queue CLI behaves similarly. > http://hadoop.apache.org/docs/stable/hadoop-yarn/hadoop-yarn-site/Resourc= eManagerRest.html#Cluster_Applications_API -- 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