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 85F5B200BD5 for ; Thu, 8 Dec 2016 20:15:02 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 84ABB160B1F; Thu, 8 Dec 2016 19:15:02 +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 CD9C2160B0A for ; Thu, 8 Dec 2016 20:15:01 +0100 (CET) Received: (qmail 61474 invoked by uid 500); 8 Dec 2016 19:15:00 -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 61247 invoked by uid 99); 8 Dec 2016 19:15:00 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Dec 2016 19:15:00 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id C63D22C03FC for ; Thu, 8 Dec 2016 19:14:59 +0000 (UTC) Date: Thu, 8 Dec 2016 19:14:59 +0000 (UTC) From: "Wangda Tan (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (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 archived-at: Thu, 08 Dec 2016 19:15:02 -0000 [ https://issues.apache.org/jira/browse/YARN-3409?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D15733= 152#comment-15733152 ]=20 Wangda Tan edited comment on YARN-3409 at 12/8/16 7:14 PM: ----------------------------------------------------------- And, bq. do you mean having an extra affinity/anti-affinity constraint expressio= n or use the same constraint expression? Probably we will need a separate o= ne. I would prefer to use the same one, this is why I suggest to name the field= to "placementStrategy" instead of "constraintExpression". To me YARN-4902 = is the goal, we should align new changes to RequestRequest to the new propo= sal. So example of how to specify anti-affinity and constraint may look like: {code} # Run on node with JDK5 or JDK6, and anti-affinity to itself's container placement-strategy =3D (JDK5 || JDK6) && anti-affinity-to # Run on node with CENTOS6 and SSD, and affinity-to application-2=20 placement-strategy =3D CENTOS6 && SSD && affinity-to application_3333_0002 {code} To make scheduler can simpler handle it, we can limit number of affinity an= d anti-affinity constraint within one placement-strategy to <=3D 1. (You ca= nnot specify {{(JDK5 && affinity-to app_1) || (JDK6 && anti-affinity-to app= _2)}}. Please share your thoughts on this. was (Author: leftnoteasy): And, bq. do you mean having an extra affinity/anti-affinity constraint expressio= n or use the same constraint expression? Probably we will need a separate o= ne. I would prefer to use the same one, this is why I suggest to name the field= to "placementStrategy" instead of "constraintExpression". To me YARN-4902 = is the goal, we should align new changes to RequestRequest to the new propo= sal. So example of how to specify anti-affinity and constraint may look like: {code} # Run on node with JDK5 or JDK6, and anti-affinity to itself's container placement-strategy =3D (JDK5 || JDK6) && anti-affinity-to # Run on node with CENTOS6 and SSD, and affinity-to application-2=20 placement-strategy =3D CENTOS6 && SSD && affinity-to application_3333_0002 {code}=20 Please share your thoughts on this. > 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: Naganarasimha G R > Attachments: Constraint-Node-Labels-Requirements-Design-doc_v1.pd= f, YARN-3409.WIP.001.patch > > > 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) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: yarn-issues-help@hadoop.apache.org