Wangda Tan commented on YARN-3409:
Thanks for comments [~xinxianyin], [~grey].
Actually you're not the first person want to make node label as a uniform
solution to the problem of locality / affinity / blacklist, etc. [~curino],
[~vinodkv] all suggested about this. Personally I think this is a good
direction, otherwise we will have separated implementation / API for all of
them, which is not clear enough. We're also looking at possibilities to put
them together to the design doc, hopefully will not take too much time.
> 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