Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 25 Jul 2017 17:46:00 +0000 (UTC)
From: "Konstantinos Karanasos (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12786252.1427474746000.9681.1501004760984@Atlassian.JIRA>
In-Reply-To: <JIRA.12786252.1427474746000@Atlassian.JIRA>
References: <JIRA.12786252.1427474746000@Atlassian.JIRA> <JIRA.12786252.1427474746215@jira-lw-us.apache.org>
Subject: [jira] [Commented] (YARN-3409) Support Node Attribute functionality
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Tue, 25 Jul 2017 17:46:09 -0000


    [ https://issues.apache.org/jira/browse/YARN-3409?page=3Dcom.atlassian.=
jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D16100=
427#comment-16100427 ]=20

Konstantinos Karanasos commented on YARN-3409:
----------------------------------------------

Thanks for the answers, [~sunilg] and [~Naganarasimha].
I think we are in sync.

[~Naganarasimha], regarding the CLI for adding/updating attributes, I see p=
oint 3 as a valid concern. Points 1 and 2 are less of an issue. We can stil=
l do multiple attributes at once, as in {{node1:java=3D8,ssd=3Dfalse}}. For=
 point 3 re: the data types, we can do something like this: {{node1:java=3D=
8\[string\],ssd=3Dfalse\[boolean\]}}. But either way, it is not a big deal.

> 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-Labe=
ls-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% mi=
nimum capacity and Dev team has 60% of minimum capacity of the partition).
> Attributes are orthogonal to partition, they=E2=80=99re describing featur=
es of node=E2=80=99s hardware/software just for affinity. Some example of a=
ttributes:
> - 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=
 >=3D 2.20 && JDK.version >=3D 8u20 && x86_64).


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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