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 850C0200D16 for ; Tue, 10 Oct 2017 15:07:06 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 837AA160BE0; Tue, 10 Oct 2017 13:07:06 +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 C97041609E5 for ; Tue, 10 Oct 2017 15:07:05 +0200 (CEST) Received: (qmail 91279 invoked by uid 500); 10 Oct 2017 13:07:05 -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 91268 invoked by uid 99); 10 Oct 2017 13:07:04 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Oct 2017 13:07:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 3DA5A19292C for ; Tue, 10 Oct 2017 13:07:04 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-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 (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id AM6PW9wCHNzC for ; Tue, 10 Oct 2017 13:07:03 +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 B1B6D61144 for ; Tue, 10 Oct 2017 13:07: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 4FAA7E105A for ; Tue, 10 Oct 2017 13:07: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 B0B45243A1 for ; Tue, 10 Oct 2017 13:07:00 +0000 (UTC) Date: Tue, 10 Oct 2017 13:07:00 +0000 (UTC) From: "lovekesh bansal (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-7312) [Resource Profiles] getMaximumAllocationPerQueue to account for all resources MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 10 Oct 2017 13:07:06 -0000 [ https://issues.apache.org/jira/browse/YARN-7312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16198644#comment-16198644 ] lovekesh bansal commented on YARN-7312: --------------------------------------- [~sunilg] I checked and found that these unit tests have already been failing in the trunk as against it seems to be failing because of the patch. Not sure how to go forward. Can you please guide? > [Resource Profiles] getMaximumAllocationPerQueue to account for all resources > ----------------------------------------------------------------------------- > > Key: YARN-7312 > URL: https://issues.apache.org/jira/browse/YARN-7312 > Project: Hadoop YARN > Issue Type: Sub-task > Affects Versions: 3.1.0 > Reporter: lovekesh bansal > Assignee: lovekesh bansal > Fix For: 3.1.0 > > Attachments: YARN-7312_trunk.001.patch > > > getMaximumAllocationPerQueue has memory and vcores hardcoded. So it should be made generic for all resources. -- 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