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 76535200C3B for ; Sat, 4 Mar 2017 01:04:53 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 74CF1160B6D; Sat, 4 Mar 2017 00:04:53 +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 BFBBE160B80 for ; Sat, 4 Mar 2017 01:04:52 +0100 (CET) Received: (qmail 87948 invoked by uid 500); 4 Mar 2017 00:04:52 -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 87937 invoked by uid 99); 4 Mar 2017 00:04:51 -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; Sat, 04 Mar 2017 00:04:51 +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 5DA96C20ED for ; Sat, 4 Mar 2017 00:04:51 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -1.547 X-Spam-Level: X-Spam-Status: No, score=-1.547 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-2.999, SPF_NEUTRAL=0.652] 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 6HdENugJlTqo for ; Sat, 4 Mar 2017 00:04:50 +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 22C1360DBE for ; Sat, 4 Mar 2017 00:04:50 +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 CC1D1E0A6C for ; Sat, 4 Mar 2017 00:04:47 +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 24C1424182 for ; Sat, 4 Mar 2017 00:04:46 +0000 (UTC) Date: Sat, 4 Mar 2017 00:04:46 +0000 (UTC) From: "Benoy Antony (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-6285) Add option to set max limit on ResourceManager for ApplicationClientProtocol.getApplications MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Sat, 04 Mar 2017 00:04:53 -0000 [ https://issues.apache.org/jira/browse/YARN-6285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15895289#comment-15895289 ] Benoy Antony commented on YARN-6285: ------------------------------------ Thanks for the patch, [~zhaoyunjiong]. Few comments: 1. {code} public static final long DEFAULT_RM_MAX_LIMIT_GET_APPLICATIONS = DEFAULT_RM_MAX_COMPLETED_APPLICATIONS; {code} I think , it's better to keep the _DEFAULT_RM_MAX_LIMIT_GET_APPLICATIONS_ independent of _DEFAULT_RM_MAX_COMPLETED_APPLICATIONS_. If we need to maintain backward compatibility, the default should be Integer.MAX_VALUE. I personally think that it should be set to 1000. 2. Please indicate the default value in the property description. 3. {code} LOG.info("User " + callerUGI.getUserName() + " called getApplications with limit=" + limit); {code} Please indicate that the value is changed to the the max value. LOG.info("User " + callerUGI.getUserName() + " called getApplications with limit=" + limit + ". Changing it to " + maxLimitGetApplications); {code} 4. {code} protected void setMaxLimitGetApplications(long limit) {code} Can it be package access instead of protected ? > Add option to set max limit on ResourceManager for ApplicationClientProtocol.getApplications > -------------------------------------------------------------------------------------------- > > Key: YARN-6285 > URL: https://issues.apache.org/jira/browse/YARN-6285 > Project: Hadoop YARN > Issue Type: Improvement > Reporter: yunjiong zhao > Assignee: yunjiong zhao > Attachments: YARN-6285.001.patch, YARN-6285.002.patch > > > When users called ApplicationClientProtocol.getApplications, it will return lots of data, and generate lots of garbage on ResourceManager which caused long time GC. > For example, on one of our RM, when called rest API " http:///ws/v1/cluster/apps" it can return 150MB data which have 944 applications. > getApplications have limit parameter, but some user might not set it, and then the limit will be Long.MAX_VALUE. -- 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