[
https://issues.apache.org/jira/browse/YARN-689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13676121#comment-13676121
]
Bikas Saha commented on YARN-689:
---------------------------------
I can see some merit in different schedulers trying out different methods to
improve fragmentation and utilization in the cluster. The multiplier seems to
be one approach to do this, though as Arun says it might make the code in the
scheduler complicated to get right. However, what I don't understand is why
this value needs to be exposed to the users via registration response. Users
are expected to ask for whatever resource they want to and they will be
allocated containers that would fit those resources. Containers will never be
smaller but may be larger than whats requested, depending on the logic
schedulers use to solve the bin-packing problem. I dont see why configs for
that logic should be exposed via API. This should be transparent to the users
and probably should be hidden from them so that schedulers can evolve. Finally,
an AM that really needs this (I don't yet see why) could probably get the value
from configuration.
> 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, 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
