[
https://issues.apache.org/jira/browse/YARN-3409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15697368#comment-15697368
]
Devaraj K commented on YARN-3409:
---------------------------------
Thanks [~Naganarasimha]/[~varun_saxena] for the document and others for the
discussion.
- {code:xml}
String labelExpression,
String constraintLabelExpression, // New modification in the
interface
{code}
- As Bibin mentioned above, 'constraintLabelExpression' naming leads to
confusion that why do we need two label expressions. I too think we need to
have different naming if we are going to have this param/configs.
- Can NodeManagers have attribute names same as some label/partition name in
the cluster? Did you think about having one expression(existing) which handles
node label expression and constraints expression without delimiter between
label and constraints expressions, constraints expression support
implementation can be added without any new configurations/interfaces.
- Can we have some details about how the NodeManager report these attributes to
ResourceManager?
> 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.pdf
>
>
> 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)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
