Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 3 Mar 2017 13:01:46 +0000 (UTC)
From: "Lantao Jin (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.13048033.1488546091000.54423.1488546106322@Atlassian.JIRA>
In-Reply-To: <JIRA.13048033.1488546091000@Atlassian.JIRA>
References: <JIRA.13048033.1488546091000@Atlassian.JIRA> <JIRA.13048033.1488546091887@jira-lw-us.apache.org>
Subject: [jira] [Created] (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
archived-at: Fri, 03 Mar 2017 13:01:53 -0000

Lantao Jin created YARN-6280:
--------------------------------

             Summary: 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
            Reporter: Lantao Jin


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://<rm http address:port>/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