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 70338200C70 for ; Thu, 20 Apr 2017 04:52:09 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 6EC56160BAD; Thu, 20 Apr 2017 02:52: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 B60BF160B9C for ; Thu, 20 Apr 2017 04:52:08 +0200 (CEST) Received: (qmail 97508 invoked by uid 500); 20 Apr 2017 02:52: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 97497 invoked by uid 99); 20 Apr 2017 02:52: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; Thu, 20 Apr 2017 02:52: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 3BBFDC0C69 for ; Thu, 20 Apr 2017 02:52:07 +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 vv0t2pp_jnrB for ; Thu, 20 Apr 2017 02:52:06 +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 1FA955FB64 for ; Thu, 20 Apr 2017 02:52:06 +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 8AEB5E0BDD for ; Thu, 20 Apr 2017 02:52:05 +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 91EF021B56 for ; Thu, 20 Apr 2017 02:52:04 +0000 (UTC) Date: Thu, 20 Apr 2017 02:52:04 +0000 (UTC) From: "Jian He (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-6280) Add a query parameter in ResourceManager Cluster Applications REST API to control whether or not returns ResourceRequest MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 20 Apr 2017 02:52:09 -0000 [ https://issues.apache.org/jira/browse/YARN-6280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15975952#comment-15975952 ] Jian He commented on YARN-6280: ------------------------------- one minor comment: how about making this generic by adding an param like: unselect="resourceRequests,..", which takes a list of unselected fields. This is more flexible and can be used to strip off more fields if there's such use case in future. > Add a query parameter in ResourceManager Cluster Applications REST API to control whether or not returns ResourceRequest > ------------------------------------------------------------------------------------------------------------------------ > > Key: YARN-6280 > URL: https://issues.apache.org/jira/browse/YARN-6280 > Project: Hadoop YARN > Issue Type: Improvement > Components: resourcemanager, restapi > Affects Versions: 2.7.3 > Reporter: Lantao Jin > Assignee: Lantao Jin > Attachments: YARN-6280.001.patch, YARN-6280.002.patch, YARN-6280.003.patch, YARN-6280.004.patch, YARN-6280.005.patch, YARN-6280.006.patch, YARN-6280.007.patch > > > Begin from v2.7, the ResourceManager Cluster Applications REST API returns ResourceRequest list. It's a very large construction in AppInfo. > As a test, we use below URI to query only 2 results: > http:///ws/v1/cluster/apps?states=running,accepted&limit=2 > The results are very different: > ||Hadoop version|Total Character|Total Word|Total Lines|Size|| > |2.4.1|1192| 42| 42| 1.2 KB| > |2.7.1|1222179| 48740| 48735| 1.21 MB| > Most RESTful API requesters don't know about this after upgraded and their old queries may cause ResourceManager more GC consuming and slower. Even if they know this but have no idea to reduce the impact of ResourceManager except slow down their query frequency. > The patch adding a query parameter "showResourceRequests" to help requesters who don't need this information to reduce the overhead. In consideration of compatibility of interface, the default value is true if they don't set the parameter, so the behaviour is the same as now. -- This message was sent by Atlassian JIRA (v6.3.15#6346) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: yarn-issues-help@hadoop.apache.org