[
https://issues.apache.org/jira/browse/YARN-6927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16205253#comment-16205253
]
Wangda Tan commented on YARN-6927:
----------------------------------
[~sunilg]/[~templedf],
bq. Could we consider other resource specifications like
yarn.app.mapreduce.am.resource.mb/cpu-vcores as a standard way to define CPU
and Memory if users want to use, rather than an overwriting model? In case when
both are specified (old and new config for cpu/memory), i am more in favor of
throwing an exception to end user asking to specify in one format.
Agreed.
> Add support for individual resource types requests in MapReduce
> ---------------------------------------------------------------
>
> Key: YARN-6927
> URL: https://issues.apache.org/jira/browse/YARN-6927
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: resourcemanager
> Reporter: Daniel Templeton
> Assignee: Gergo Repas
> Attachments: YARN-6927.000.patch, YARN-6927.001.patch
>
>
> YARN-6504 adds support for resource profiles in MapReduce jobs, but resource
> profiles don't give users much flexibility in their resource requests. To
> satisfy users' needs, MapReduce should also allow users to specify arbitrary
> resource requests.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
