[
https://issues.apache.org/jira/browse/YARN-689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13677516#comment-13677516
]
Alejandro Abdelnur commented on YARN-689:
-----------------------------------------
Based on the discussion in YARN-769, I got the memory utilization concern, more
than fragmentation it is a leftover issue.
Hitesh, Bikas, you have a point, I think we remove the minimum from the API.
I'll open a MAPREDUCE JIRA to eliminate the use of minimum there first, then a
new YARN JIRA to remove the minimum from the API.
Finally, to support by use case of zero resources in one dimension, the
schedulers should have min and increment config values. In short, what this
JIRA introduces without any exposure on the APIs.
Sounds good?
> Add multiplier unit to resourcecapabilities
> -------------------------------------------
>
> Key: YARN-689
> URL: https://issues.apache.org/jira/browse/YARN-689
> Project: Hadoop YARN
> Issue Type: Sub-task
> 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,
> 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
