[
https://issues.apache.org/jira/browse/YARN-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15098511#comment-15098511
]
Karthik Kambatla commented on YARN-1011:
----------------------------------------
[~nroberts], [~leftnoteasy] - reasonable concerns. I am looking into allowing
the app ask only for guaranteed containers. Scheduling will likely remain
simple: in our loop, we just skip an application if it is not interested in
opportunistic containers. Promotion, though, becomes tricky: we should hold off
on promoting a container until all higher-"priority" applications that want
only guaranteed containers get them.
Welcome any thoughts/suggestions on handling promotion if we allow applications
to ask for only guaranteed containers. I ll continue brain-storming. We want to
have a simple mechanism, if possible; complex protocols seem to find a way to
hoard bugs.
> [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: 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)
