[
https://issues.apache.org/jira/browse/YARN-689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13662147#comment-13662147
]
Hitesh Shah commented on YARN-689:
----------------------------------
[~sandyr] - good point. [~tucu00] - I am not too sure about both the use-case
where a minimum of zero is allowed - I am guessing the scheduler implementation
will need to be extra careful about how to do such allocations if allowed at
all.
Seems like there are multiple cases where multiplier alone may not be enough. I
am +0 on this. I would defer to [~acmurthy] and [~bikassaha] if either of them
have any concerns on the scheduler implementations with respect to how this
feature affects likely affected features such as reservations.
> 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
