[
https://issues.apache.org/jira/browse/YARN-689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13662630#comment-13662630
]
Alejandro Abdelnur edited comment on YARN-689 at 5/21/13 3:21 AM:
------------------------------------------------------------------
Here it goes again: I have an additional use case where decoupling the minimum
and the multiplier would lead to a significantly better resource utilization. I
have an application that does container allocations using pure memory or pure
CPU. This is, it requests containers with only CPU capabilities or with only
memory capabilities. In this scenario, the minimum would be set to ZERO. The
overload of min/multiplier does not work in this case.
was (Author: tucu00):
Here it goes again: I have an additional use case where decoupling the
minimum and the multiplier would lead to a significantly better resource
utilization. I have an application that does container allocations using pure
memory or pure CPU. This is, it requests containers with only CPU capabilities
or with only memory capabilities. In this scenario, the minimum would bet set
to ZERO. The overload of min/multiplier does not work in this case.
> 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
