From yarn-issues-return-108802-apmail-hadoop-yarn-issues-archive=hadoop.apache.org@hadoop.apache.org Tue Feb 28 03:06:47 2017 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 D21A819642 for ; Tue, 28 Feb 2017 03:06:47 +0000 (UTC) Received: (qmail 91902 invoked by uid 500); 28 Feb 2017 03:06:47 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 91862 invoked by uid 500); 28 Feb 2017 03:06:47 -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 91851 invoked by uid 99); 28 Feb 2017 03:06:47 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Feb 2017 03:06:47 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 34AA7C19D6 for ; Tue, 28 Feb 2017 03:06:47 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.451 X-Spam-Level: * X-Spam-Status: No, score=1.451 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_NEUTRAL=0.652] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id xT233lRf_GVI for ; Tue, 28 Feb 2017 03:06:46 +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 6446F5FB0B for ; Tue, 28 Feb 2017 03:06:46 +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 C9EC5E055F for ; Tue, 28 Feb 2017 03:06:45 +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 5835824134 for ; Tue, 28 Feb 2017 03:06:45 +0000 (UTC) Date: Tue, 28 Feb 2017 03:06:45 +0000 (UTC) From: "Sunil G (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-6243) CapacityScheduler: canAssignToThisQueue should be called only when necessary 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-6243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15887143#comment-15887143 ] Sunil G commented on YARN-6243: ------------------------------- During async sync thread allocation, is it possible that queue used may be changed? If queue used is not changed, may {{canAssignToThisQueue}} need not have to be invoked provided there are no resource changes in cluster (add/remove node). Is this what you are also thinking? > CapacityScheduler: canAssignToThisQueue should be called only when necessary > ---------------------------------------------------------------------------- > > Key: YARN-6243 > URL: https://issues.apache.org/jira/browse/YARN-6243 > Project: Hadoop YARN > Issue Type: Sub-task > Reporter: Wangda Tan > > Now canAssignToThisQueue is called when iterating apps in a LeafQueue, we should optimize this. -- 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