hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Varun Vasudev (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3926) Extend the YARN resource model for easier resource-type management and profiles
Date Wed, 16 Mar 2016 14:54:33 GMT

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

Varun Vasudev commented on YARN-3926:
-------------------------------------

[~asuresh] - I was speaking with [~leftnoteasy] offline. I suspect we'll have to support 3
modes for the RM-NM handshake which admins can configure  -
# Strict - the RM and NM resource types must match
# 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?
# Allow mismatch - the handshake will not fail due to missing resource types - missing resource
types are presumed to be of value 0 by the RM.

Does that make sense?

> 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)

Mime
View raw message