[
https://issues.apache.org/jira/browse/YARN-689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13677181#comment-13677181
]
Hitesh Shah commented on YARN-689:
----------------------------------
[~tucu00] [~bikassaha] Should we just remove min allocation ( aka the
multiplier/increment ) from the APIs/protocol as it seems to be a scheduler
specific internal artifact? The only requirement from an API point of view
seems to be the max allocation as a request greater than max will trigger an
exception from the RM. A request less than min could be rounded up as needed by
the scheduler based on its implementation. An application need to know how its
request will be rounded up or down. It simply asks for something and gets a
container based on its ask ( that need not exactly match what it had asked for
).
The MR AM should not need round off its container requests based on RM's
min(increment) setting. It just needs to be able to handle allocations which
are slightly more than what it originally asked for based on the current
scheduler implementations.
With the above change, the min+increment settings could then be
scheduler-implementation specific settings that do not spill over into the
api/protocol.
> 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
