[
https://issues.apache.org/jira/browse/YARN-6927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16210123#comment-16210123
]
Daniel Templeton commented on YARN-6927:
----------------------------------------
# In {{getCustomResourceTypePrefix()}}, the {{Optional}} is overkill. You
could just return null.
# In {{TaskAttemptImpl()}}, {{resourceInformation}} isn't used, which means the
resource types are ignored, and we only use the old style properties.
# It looks like we're now just ignoring the am_prefix.mb and
am_prefix.cpu-vcores properties. We should only ignore them if there's a
conflict.
> 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-6927.002.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]
