[
https://issues.apache.org/jira/browse/YARN-6927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16205010#comment-16205010
]
Daniel Templeton commented on YARN-6927:
----------------------------------------
Agree about the space.
I see the point that a user you specifies both the old and new options might be
confused by the result. On the other hand, it's confusing to have some of the
options use the new format, and some the old. I think I'd rather not throw an
exception on the new format. If you're really worried about confusing the
user, we could throw an exception if the user specifies both the new and old
memory values (or same for CPU).
> 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: [email protected]
For additional commands, e-mail: [email protected]