[
https://issues.apache.org/jira/browse/YARN-689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Abdelnur updated YARN-689:
------------------------------------
Attachment: YARN-689.patch
Rebasing patch to trunk.
Changed new property name from 'multiplier' to 'increment' as it is more clear
of the intend.
Set the default value of resource increment to be the resource minimum. A
increment different from the minimum will only be in place if increment is set
in the yarn-site.xml file, otherwise the increment always matches the minimum
(the current behavior).
Adding to my last comment on why this should be in the API. By being in the
API, client can ask the RM without relying on having the RM configuration
locally available. Also, it provides consistent behavior across Scheduler
implementations.
> 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,
> 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
