[
https://issues.apache.org/jira/browse/YARN-4512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15115711#comment-15115711
]
Inigo Goiri commented on YARN-4512:
-----------------------------------
I'm OK with not using the {{ResourceOption}} approach itself. I'm more
concerned about sending the over-allocation value on the heartbeat; wouldn't
make more sense to send it on registration? The restart approach you mention
would work there.
Other than that, it 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, 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)
