[ 
https://issues.apache.org/jira/browse/YARN-689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13660874#comment-13660874
 ] 

Alejandro Abdelnur commented on YARN-689:
-----------------------------------------

There is a headroom that YARN requires, that is YARN_MINIMUM = YARN_HEADROOM.

Then, as you said, there it is headroom specific to each up, APP_MINIMUM = 
YARN_MINIMUM + APP_HEADROOM.

Then, there is the multiplier that defines the valid increments (which are used 
for normalization).

Going to a concret example, using increments of 256MB seems a reasonable unit, 
but if you set your YARN_MINIMUM to 256MB you'll run OOM doing basic stuff.

Furthermore, given how things have been in the past, I see the headroom 
required by the framework growing, thus requiring the YARN_MIN to increase. And 
if the minimum stays tied to the multipler it will lead to under utilization.

What is the concern of having a multiplier that allows decoupling the minimum 
from the multiplier? What is conceptually wrong with it? We could have the 
default tied up to minimum, thus preserving current behavior.

                
> 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
>
>
> 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

Reply via email to