[
https://issues.apache.org/jira/browse/YARN-3409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16304118#comment-16304118
]
Naganarasimha G R commented on YARN-3409:
-----------------------------------------
Thanks [~cheersyang] for looking into this jira and the design Doc,
bq. then there is a request asking for NUM_OF_DISKS > 3, there is only 1 node
satisfy this requirement but its resource is already used up by other
containers. What will happen here? Will you preempt containers on this node to
make room for such request?
Attribute based scheduling is more like best effort basis and doesn't guarantee
capacity guarantee across attribute labels, as a given node can have multiple
attributes and scheduling might happen based on a subset of attributes. Hence
it would be impossible to preempt as it might lead to cyclic pre-emptions. So
if guaranteed resources based on a specific label is the requirement then we
need to use {{"Partition Labels"}}.
But well the api's which are coming in YARN-6592 will help to specify for an
container how long to wait and they try with other options. so hard and soft on
the request side can be controlled (though not on the allocation side which you
were expecting)
> Support Node Attribute functionality
> ------------------------------------
>
> Key: YARN-3409
> URL: https://issues.apache.org/jira/browse/YARN-3409
> Project: Hadoop YARN
> Issue Type: New Feature
> Components: api, client, RM
> Reporter: Wangda Tan
> Assignee: Naganarasimha G R
> Attachments: 3409-apiChanges_v2.pdf (4).pdf,
> Constraint-Node-Labels-Requirements-Design-doc_v1.pdf, YARN-3409.WIP.001.patch
>
>
> 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).
> Attributes are orthogonal to partition, they’re describing features of node’s
> hardware/software just for affinity. Some example of attributes:
> - 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.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
