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 DEF4B18BF2 for ; Thu, 25 Jun 2015 16:39:06 +0000 (UTC) Received: (qmail 59779 invoked by uid 500); 25 Jun 2015 16:39:05 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 59727 invoked by uid 500); 25 Jun 2015 16:39: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 59716 invoked by uid 99); 25 Jun 2015 16:39:05 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Jun 2015 16:39:05 +0000 Date: Thu, 25 Jun 2015 16:39:05 +0000 (UTC) From: "chong chen (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-3409) Add constraint node labels MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/YARN-3409?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D14601= 495#comment-14601495 ]=20 chong chen commented on YARN-3409: ---------------------------------- Any update on this?=20 > Add constraint node labels > -------------------------- > > Key: YARN-3409 > URL: https://issues.apache.org/jira/browse/YARN-3409 > Project: Hadoop YARN > Issue Type: Sub-task > Components: api, capacityscheduler, client > Reporter: Wangda Tan > Assignee: Wangda Tan > > Specify only one label for each node (IAW, partition a cluster) is a way = to determinate how resources of a special set of nodes could be shared by a= group of entities (like teams, departments, etc.). Partitions of a cluster= has following characteristics: > - Cluster divided to several disjoint sub clusters. > - ACL/priority can apply on partition (Only market team / marke team has = priority to use the partition). > - Percentage of capacities can apply on partition (Market team has 40% mi= nimum capacity and Dev team has 60% of minimum capacity of the partition). > Constraints are orthogonal to partition, they=E2=80=99re describing attri= butes of node=E2=80=99s hardware/software just for affinity. Some example o= f constraints: > - glibc version > - JDK version > - Type of CPU (x86_64/i686) > - Type of OS (windows, linux, etc.) > With this, application can be able to ask for resource has (glibc.version= >=3D 2.20 && JDK.version >=3D 8u20 && x86_64). -- This message was sent by Atlassian JIRA (v6.3.4#6332)