[
https://issues.apache.org/jira/browse/YARN-3409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15686590#comment-15686590
]
Bibin A Chundatt commented on YARN-3409:
----------------------------------------
Thank you [[email protected]] for uploading design doc
Few comments
# We should call current feature as NodeConstraints since we have label is
considered as cluster partition.Resource request as constraintsExpression
instead of constraintslabelexpression.
# Nodes with same Constraints could be in multiple partition,so are we allowing
resource to serve any labels satisfying constraints or only subset of label
resource pool satisfying constraints.
# At RM side is it required to have a constraints list?.We could consider all
constraints or attributes with which NM registers.For dynamic updation its
better that way rt?
# Any relaxation similar to node locality.If request doesnt satisfy constraints
will it ever serve request.If we are planning to support then addition
attribute in ResourceRequest.
# We could also support default constraints {{DISK,CPUS,JAVA version etc}}.Are
we planning to report from Nodemanager these default constraints. Will NM try
to autodetect the resources available at the local machine ??Any interface in
NM to add custom auto identifiers based on constraints.
# ResourceRequest interface : +1 to option 1 as you mentioned other approaches
seems to be more of an alternate approach than a concrete solution.
> 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: [email protected]
For additional commands, e-mail: [email protected]
