[
https://issues.apache.org/jira/browse/YARN-3926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15952056#comment-15952056
]
Zhankun Tang commented on YARN-3926:
------------------------------------
{quote}
As mentioned above, the overrides will only be allowed for memory and cpu.
We also propose a config flag to enable/disable overrides(set to enable
overrides by default)
using which admins can turn off the override behaviour.
{quote}
[~vvasudev], I have doubt on that in the design doc. Could you please explain
the reason why we only allow cpu and memory overriding in resource profile?
How about we make it by default and provide configurations/options to switch
on/off the resource that can be override?
I'd like to help on this if we need this. :)
> 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.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
