[
https://issues.apache.org/jira/browse/YARN-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15171244#comment-15171244
]
Bikas Saha commented on YARN-1011:
----------------------------------
bq. If it absolutely wants a guaranteed container, we should allocate a
guaranteed container and kill the opportunistic one. If it does not want, we
can let the opportunistic container continue to run.
I get that. The question is which of the 2 is the default behavior?
Next question to consider: If we let the opportunistic container run and
consider it as part of guaranteed capacity then what prevents the node from
killing it when the node resources get actually over-used and something needs
to be killed by the node. And how does the rest of the system (yarn + app)
react to losing a guaranteed container?
bq. The overall cluster utilization is an implementation detail, its sole
purpose is to reduce the chances of running into cases that need cross-node
promotion.
I am sorry I could not understand how that is so?
> [Umbrella] Schedule containers based on utilization of currently allocated
> containers
> -------------------------------------------------------------------------------------
>
> Key: YARN-1011
> URL: https://issues.apache.org/jira/browse/YARN-1011
> Project: Hadoop YARN
> Issue Type: New Feature
> Reporter: Arun C Murthy
> Attachments: patch-for-yarn-1011.patch, yarn-1011-design-v0.pdf,
> yarn-1011-design-v1.pdf, yarn-1011-design-v2.pdf
>
>
> Currently RM allocates containers and assumes resources allocated are
> utilized.
> RM can, and should, get to a point where it measures utilization of allocated
> containers and, if appropriate, allocate more (speculative?) containers.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
