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 "lovekesh bansal (JIRA)" <ji...@apache.org> on 2017/10/10 05:41:00 UTC
[jira] [Comment Edited] (YARN-7312) [Resource Profiles]
getMaximumAllocationPerQueue to account for all resources
[ https://issues.apache.org/jira/browse/YARN-7312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16198186#comment-16198186 ]
lovekesh bansal edited comment on YARN-7312 at 10/10/17 5:40 AM:
-----------------------------------------------------------------
V1 Patch uploaded for umbrella YARN-7069.
was (Author: lovekesh.bansal):
V1 Patch uploaded.
> [Resource Profiles] getMaximumAllocationPerQueue to account for all resources
> -----------------------------------------------------------------------------
>
> Key: YARN-7312
> URL: https://issues.apache.org/jira/browse/YARN-7312
> Project: Hadoop YARN
> Issue Type: Task
> Affects Versions: 3.1.0
> Reporter: lovekesh bansal
> Fix For: 3.1.0
>
> Attachments: YARN-7312_trunk.001.patch
>
>
> getMaximumAllocationPerQueue has memory and vcores hardcoded. So it should be made generic for all resources.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org