[
https://issues.apache.org/jira/browse/YARN-4512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15091330#comment-15091330
]
Inigo Goiri commented on YARN-4512:
-----------------------------------
Regarding the overallocation vs oversubscription, I'm more concerned about
consistency, an example is {{Context}} in the NM:
{code}
boolean isOverSubscriptionEnabled();
OverAllocationInfo getOverAllocationInfo();
{code}
Regarding the RM knowing about the preemption in the parameter:
bq. The preemption happens on the NM. Theoretically, the RM might want to keep
track of this and aggressively make some decisions. No concrete ideas at the
moment, so left it out. Any suggestions on how we could use preemption
information on RM?
I'd say the RM should know what the NM is doing, otherwise, after a container
preemption, the RM may try to keep doing the same and the NM preempting again.
Everything else looks good.
> 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
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
