You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "David Villegas (JIRA)" <ji...@apache.org> on 2015/04/22 16:35:59 UTC

[jira] [Commented] (YARN-3409) Add constraint node labels

    [ https://issues.apache.org/jira/browse/YARN-3409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14507169#comment-14507169 ] 

David Villegas commented on YARN-3409:
--------------------------------------

Hi [~wangda],

Are you planning to make the constraints static, i.e., set by an administrator? Or dynamic, so that they could reflect the current state of the cluster? I was wondering if this type of labels could be used to implement anti-affinity as described in YARN-1042. It seems to me this feature could potentially be similar to [Condor ClassAds|http://research.cs.wisc.edu/htcondor/manual/v7.6/4_1Condor_s_ClassAd.html], where a container request could specify things like the average load of the machine, or whether it is already running containers for a particular application type.

> 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% minimum capacity and Dev team has 60% of minimum capacity of the partition).
> Constraints are orthogonal to partition, they’re describing attributes of node’s hardware/software just for affinity. Some example of 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 >= 2.20 && JDK.version >= 8u20 && x86_64).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)