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 3F131200CE7 for ; Wed, 2 Aug 2017 19:27:05 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 3DDC7169F5E; Wed, 2 Aug 2017 17:27:05 +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 839A8169F5F for ; Wed, 2 Aug 2017 19:27:04 +0200 (CEST) Received: (qmail 77909 invoked by uid 500); 2 Aug 2017 17:27:03 -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 77892 invoked by uid 99); 2 Aug 2017 17:27:03 -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; Wed, 02 Aug 2017 17:27:03 +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 26454C0221 for ; Wed, 2 Aug 2017 17:27:03 +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-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id BDiRRMtE5Cxp for ; Wed, 2 Aug 2017 17:27:02 +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 97D555F6C8 for ; Wed, 2 Aug 2017 17:27:01 +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 D5B01E0999 for ; Wed, 2 Aug 2017 17:27:00 +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 797122464D for ; Wed, 2 Aug 2017 17:27:00 +0000 (UTC) Date: Wed, 2 Aug 2017 17:27:00 +0000 (UTC) From: "Giovanni Matteo Fumarola (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-6871) Add a new REST API GetAppReport call lighter and faster than the current one MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 02 Aug 2017 17:27:05 -0000 [ https://issues.apache.org/jira/browse/YARN-6871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16111364#comment-16111364 ] Giovanni Matteo Fumarola commented on YARN-6871: ------------------------------------------------ Good feedback [~subru] and good work on YARN-6280 [~sunilg]. Let me update the title and the description. > Add a new REST API GetAppReport call lighter and faster than the current one > ---------------------------------------------------------------------------- > > Key: YARN-6871 > URL: https://issues.apache.org/jira/browse/YARN-6871 > Project: Hadoop YARN > Issue Type: New Feature > Components: resourcemanager, router > Reporter: Giovanni Matteo Fumarola > > This jira tracks the effort to create a new REST API similar to the current GetAppReport but lighter and faster. > With the current one we are facing a scalability issues. > E.g. with ~500 applications running the AppReport can reach up to 300MB in size due to the {{ResourceRequest}} in the {{AppInfo}}. > The new method returns for each application the following and essential information: > * The application id; > * The application name; > * The application state according to the ResourceManager - valid values are members of the YarnApplicationState enum: NEW, NEW_SAVING, SUBMITTED, ACCEPTED, RUNNING, FINISHED, FAILED, KILLED; > * The final status of the application if finished - reported by the application itself - valid values are: UNDEFINED, SUCCEEDED, FAILED, KILLED; > * The web URL that can be used to track the application; > * Detailed diagnostics information; > * The URL of the application master container logs; > * The nodes http address of the application master; > * The progress of the application as a percent. > Yarn RM will return the new result faster and it will use less compute cycles to create the report and it will improve the YARN RM and Client's performances. -- 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