You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Sunil G (JIRA)" <ji...@apache.org> on 2018/02/13 08:01:00 UTC
[jira] [Comment Edited] (YARN-7292) Revisit Resource Profile
Behavior
[ https://issues.apache.org/jira/browse/YARN-7292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16361948#comment-16361948 ]
Sunil G edited comment on YARN-7292 at 2/13/18 8:00 AM:
--------------------------------------------------------
Thanks [~leftnoteasy]. I am not very sure about that option "do-not-override" is needed, as we have some cleaner option like zero capability from utils (or from server). Other than the patch looks fine to me +1.
was (Author: sunilg):
Thanks [~leftnoteasy]. I am not very sure about that option "do-not-override" is needed, as we have some cleaner option like zero capability from utils (or from server).
> Revisit Resource Profile Behavior
> ---------------------------------
>
> Key: YARN-7292
> URL: https://issues.apache.org/jira/browse/YARN-7292
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: nodemanager, resourcemanager
> Reporter: Wangda Tan
> Assignee: Wangda Tan
> Priority: Blocker
> Attachments: YARN-7292.002.patch, YARN-7292.003.patch, YARN-7292.004.patch, YARN-7292.005.patch, YARN-7292.006.patch, YARN-7292.wip.001.patch
>
>
> Had discussions with [~templedf], [~vvasudev], [~sunilg] offline. There're a couple of resource profile related behaviors might need to be updated:
> 1) Configure resource profile in server side or client side:
> Currently resource profile can be only configured centrally:
> - Advantages:
> A given resource profile has a the same meaning in the cluster. It won’t change when we run different apps in different configurations. A job can run under Amazon’s G2.8X can also run on YARN with G2.8X profile. A side benefit is YARN scheduler can potentially do better bin packing.
> - Disadvantages:
> Hard for applications to add their own resource profiles.
> 2) Do we really need mandatory resource profiles such as minimum/maximum/default?
> 3) Should we send resource profile name inside ResourceRequest, or should client/AM translate it to resource and set it to the existing resource fields?
> 4) Related to above, should we allow resource overrides or client/AM should send final resource to RM?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org