hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sunil G (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3409) Support Node Attribute functionality
Date Tue, 25 Jul 2017 02:15:03 GMT

    [ https://issues.apache.org/jira/browse/YARN-3409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16099399#comment-16099399

Sunil G commented on YARN-3409:

Thanks [~kkaranasos] for comments.

Some quick thoughts here.
bq.is the plan to use the new constraints API we are introducing in YARN-6593?
Yes, you are correct. We will be using new api set from YARN-6593. There are some minor thoughts
in relation with that, i ll add same in YARN-6593.

bq.In the CLI API the replace and update seem a bit confusing to me ...
Adding some more thoughts. In line with [~leftnoteasy] comments, {{replace}} is a single operation,
since it is a superset of {{remove}} and {{remove+add}}. We support this in existing node
labels with a similar command but syntax is sometime confusing. And I think, and as also mentioned
above, {{add}} / {{remove}} will be an operation which may be more happening in system. {{replace}}
might be happening when we take system to maintenance mode and do some upgrades. I think more
descriptive help seems a very nice addition and better documentation. for cli, we ll handle

> 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, capacityscheduler, client
>            Reporter: Wangda Tan
>            Assignee: Naganarasimha G R
>         Attachments: 3409-apiChanges_v2.pdf (4).pdf, 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).
> 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

To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org

View raw message