Wangda Tan commented on YARN-3409:
Thanks for pointing the Condor's dynamic label, I haven't considered this
before. I'm not sure if dynamic label is useful or not, may be loadAvg is not a
very good example: It is very possible that a container get allocated on a node
with loadAvg = 0.1 but soon it becomes 0.5 after we launched the container,
there will be no guarantee here.
For the dynamic label itself, I think we should be able to support it. Node can
update labels when doing heartbeat with AM.
> 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