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

Lei Guo commented on YARN-3926:
-------------------------------

Another topic related to rm-nm protocol is  constraint label. It's not a must 
to be considered in this Jira, but I'd like to raise it as I can see the design 
in this Jira may affect the constraint label one. 

The constraint label could be some server attribute reported by NM, it could be 
required to be predefined in RM, but if we can allow NM to define something not 
defined in RM, and then RM automatically add it in label repository, it will be 
great. for example, for OS version or JDK version, customer may prefer 
automatically added instead of adding label before use.

> Extend the YARN resource model for easier resource-type management and 
> profiles
> -------------------------------------------------------------------------------
>
>                 Key: YARN-3926
>                 URL: https://issues.apache.org/jira/browse/YARN-3926
>             Project: Hadoop YARN
>          Issue Type: New Feature
>          Components: nodemanager, resourcemanager
>            Reporter: Varun Vasudev
>            Assignee: Varun Vasudev
>         Attachments: Proposal for modifying resource model and profiles.pdf
>
>
> Currently, there are efforts to add support for various resource-types such 
> as disk(YARN-2139), network(YARN-2140), and  HDFS bandwidth(YARN-2681). These 
> efforts all aim to add support for a new resource type and are fairly 
> involved efforts. In addition, once support is added, it becomes harder for 
> users to specify the resources they need. All existing jobs have to be 
> modified, or have to use the minimum allocation.
> This ticket is a proposal to extend the YARN resource model to a more 
> flexible model which makes it easier to support additional resource-types. It 
> also considers the related aspect of “resource profiles” which allow users to 
> easily specify the various resources they need for any given container.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to