[
https://issues.apache.org/jira/browse/YARN-6927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16206035#comment-16206035
]
Gergo Repas commented on YARN-6927:
-----------------------------------
Thanks - good points. I started to amend my patch according to the above
comments, and ran into the issue that mapreduce.map.cpu.vcores=1 is present in
mapred-default.xml, so when I specify the new config
(mapreduce.reduce.resource.cpu-vcores) an exception is thrown, due to both old
and new config being present. Should I update the old config key to the new one
in mapred-default.xml? I'm not sure how existing, already deployed
mapred-default.xml-s could be handled - is there any place I can add this as a
migration step?
> 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
