[
https://issues.apache.org/jira/browse/YARN-3926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15197750#comment-15197750
]
Arun Suresh commented on YARN-3926:
-----------------------------------
bq. RM subset - as long the NM resource types are a superset of the RM, the
handshake proceeds - I believe this will address your concerns. Correct?
That should work... But I feel, maybe *allow mismatch* should be the default.
If NM has a super-set of RMs resource types, it will just be ignored, If
sub-set, then for those specific resource-types, RM will assign a 0 value for
the NM.
Which would facilitate my other point.. Allow NMs to dynamically advertise new
/ disable existing resource types (NM would know of these new types via some
admin API or self-discovery) as part of the NM heartbeat. Similarly, on the RM
side, if the new resource advertised by the NM is unknown to RM, it just
ignores it. We can also add admin API on the RM to add / remove allowable
resource types on the fly.
> 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)
