Return-Path: X-Original-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 21D5A10332 for ; Fri, 27 Feb 2015 19:53:05 +0000 (UTC) Received: (qmail 69161 invoked by uid 500); 27 Feb 2015 19:53:05 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 69119 invoked by uid 500); 27 Feb 2015 19:53:05 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: yarn-issues@hadoop.apache.org Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 68948 invoked by uid 99); 27 Feb 2015 19:53:04 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 27 Feb 2015 19:53:04 +0000 Date: Fri, 27 Feb 2015 19:53:04 +0000 (UTC) From: "Wangda Tan (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-3278) Queue's current-max-limit should be updated when container allocated/released in another queue MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/YARN-3278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14340711#comment-14340711 ] Wangda Tan commented on YARN-3278: ---------------------------------- One possible solution is forced update current-max-limit of *all* queues when resource updated (container allocated/released, etc.). But this may lead to performance regression, we should verify this plan is efficiency before doing that. > Queue's current-max-limit should be updated when container allocated/released in another queue > ---------------------------------------------------------------------------------------------- > > Key: YARN-3278 > URL: https://issues.apache.org/jira/browse/YARN-3278 > Project: Hadoop YARN > Issue Type: Sub-task > Components: capacityscheduler, resourcemanager > Reporter: Wangda Tan > Assignee: Wangda Tan > > This is a problem after YARN-2008, queue's current-max-limit (it was called maxAvailCapacity in YARN-2008) will be updated when queue is traversed by scheduler, so application can get headroom based on staled current-max-limit. For example: > {code} > r > / \ > a b > / \ > a1 b1 > ^ ^ > | | > app1 app2 > {code} > We have above queue structure, two apps in the cluster: app1 in a1, and app2 in b1. If scheduler always travers b1 only, and continously allocate containers in b1, app1's headroom will not get updated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)