[
https://issues.apache.org/jira/browse/YARN-6927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gergo Repas updated YARN-6927:
------------------------------
Attachment: YARN-6927.004.patch
Thanks for the comments [~templedf].
1 - I think we have not discussed this before, but sounds good. I added this to
YARN-6927.004.patch, and made sure that only one of these resource names can be
specified at once. I also renamed cpu-vcores to vcores.
2 - Good point. I've been using ResourceUtils.getDefaultUnit() to fall back to
the default unit if the user did not provide one (this piece of code is in
ResourceUtils.getRequestedResourcesFromConfig()), but the getDefaultUnit()
method returns no units for "memory" by default - I added some special handling
into TaskAttemptImpl and YARNRunner for this.
> 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-6927.003.patch, YARN-6927.004.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]
