[
https://issues.apache.org/jira/browse/YARN-4512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15096891#comment-15096891
]
Inigo Goiri commented on YARN-4512:
-----------------------------------
I think you both guys are saying the same: (1) the NM will have the
overallocation parameter that says how much extra the RM can place in a node
and then, (2) the RM (probably in YARN-4511) will decide to allocate more
containers than the amount of resources.
After thinking about it, I think it makes more sense to send this
overallocaiton parameter in the registration instead of the heartbeat. If we
want to dynamically change the overallocaiton we may want to do it as the
ResourceOption does.
> Provide a knob to turn on over-allocation
> -----------------------------------------
>
> Key: YARN-4512
> URL: https://issues.apache.org/jira/browse/YARN-4512
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: nodemanager
> Reporter: Karthik Kambatla
> Assignee: Karthik Kambatla
> Attachments: YARN-4512-YARN-1011.001.patch,
> yarn-4512-yarn-1011.002.patch, yarn-4512-yarn-1011.003.patch
>
>
> We need two configs for overallocation - one to specify the threshold upto
> which it is okay to over-allocate, another to specify the threshold after
> which OPPORTUNISTIC containers should be preempted.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
