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 1875910497 for ; Tue, 17 Mar 2015 21:43:45 +0000 (UTC) Received: (qmail 93092 invoked by uid 500); 17 Mar 2015 21:43:38 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 93044 invoked by uid 500); 17 Mar 2015 21:43:38 -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 93031 invoked by uid 99); 17 Mar 2015 21:43:38 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Mar 2015 21:43:38 +0000 Date: Tue, 17 Mar 2015 21:43:38 +0000 (UTC) From: "Wangda Tan (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (YARN-3361) CapacityScheduler side changes to support non-exclusive node labels 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-3361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-3361: ----------------------------- Component/s: (was: api) (was: client) (was: resourcemanager) capacityscheduler > CapacityScheduler side changes to support non-exclusive node labels > ------------------------------------------------------------------- > > Key: YARN-3361 > URL: https://issues.apache.org/jira/browse/YARN-3361 > Project: Hadoop YARN > Issue Type: Sub-task > Components: capacityscheduler > Reporter: Wangda Tan > Assignee: Wangda Tan > > According to design doc attached in YARN-3214, we need implement following logic in CapacityScheduler: > 1) When allocate a resource request with no node-label specified, it should get preferentially allocated to node without labels. > 2) When there're some available resource in a node with label, they can be used by applications with following order: > - Applications under queues which can access the label and ask for same labeled resource. > - Applications under queues which can access the label and ask for non-labeled resource. > - Applications under queues cannot access the label and ask for non-labeled resource. > 3) Expose necessary information that can be used by preemption policy to make preemption decisions. -- This message was sent by Atlassian JIRA (v6.3.4#6332)