[
https://issues.apache.org/jira/browse/YARN-689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13663042#comment-13663042
]
Hitesh Shah commented on YARN-689:
----------------------------------
[~tucu00] Regardless of whether an app is more cpu-intensive or memory-bound,
it will always utilize some of the other resources. DRF could solve the issue
in any case where the appropriate weight of the more important resource will
drive the allocation. Allowing 0 to be set as a resource ask seems to likely to
error prone allocations with more stringent checks required to ensure that a
single node does not become too overloaded.
Could you explain why your application cannot do something like the following:
- the container that needs pure CPU asks for 7 cores and 1 GB
- the container that needs pure memory asks for 7 GB and 1 core.
> 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
