[
https://issues.apache.org/jira/browse/YARN-689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13671069#comment-13671069
]
Arun C Murthy commented on YARN-689:
------------------------------------
bq. A request comes in for 20MB, .5CPUs(cpu_shares in cgroups), 1 booster_rock,
and 3 GPUs. That request is then evaluated against an
expression(min,max,whatever) during the activation time, which then splices the
resource appropriately.
[~tstclair] YARN already supports this (see YARN-2). That is a more direct way
- we don't want to be proxying one resource-type with the other. We already did
that in MR1 (everything was modeled as RAM) and we are done with that here.
> Add multiplier unit to resourcecapabilities
> -------------------------------------------
>
> Key: YARN-689
> URL: https://issues.apache.org/jira/browse/YARN-689
> Project: Hadoop YARN
> Issue Type: Bug
> Components: api, scheduler
> Affects Versions: 2.0.4-alpha
> Reporter: Alejandro Abdelnur
> Assignee: Alejandro Abdelnur
> Attachments: YARN-689.patch, YARN-689.patch, YARN-689.patch
>
>
> Currently we overloading the minimum resource value as the actual multiplier
> used by the scheduler.
> Today with a minimum memory set to 1GB, requests for 1.5GB are always
> translated to allocation of 2GB.
> We should decouple the minimum allocation from the multiplier.
> The multiplier should also be exposed to the client via the
> RegisterApplicationMasterResponse
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
