[ 
https://issues.apache.org/jira/browse/YARN-2882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15059318#comment-15059318
 ] 

Wangda Tan edited comment on YARN-2882 at 12/16/15 1:50 AM:
------------------------------------------------------------

bq. That said, we could use the naming "opportunistic" for both cases, but we 
will need an extra flag that determines whether overcommitment is enabled.

I would prefer the above proposal. Overcommitment/queueable are just two 
different approaches to handle "extra" allocated containers.


was (Author: leftnoteasy):
bq. That said, we could use the naming "opportunistic" for both cases, but we 
will need an extra flag that determines whether overcommitment is enabled.

I would prefer the above proposal. Overcommitment/queueable are two different 
just approaches to handle "extra" allocated containers.

> Add ExecutionType to denote if a container execution is GUARANTEED or 
> QUEUEABLE
> -------------------------------------------------------------------------------
>
>                 Key: YARN-2882
>                 URL: https://issues.apache.org/jira/browse/YARN-2882
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: nodemanager, resourcemanager
>            Reporter: Konstantinos Karanasos
>            Assignee: Konstantinos Karanasos
>         Attachments: YARN-2882-yarn-2877.001.patch, 
> YARN-2882-yarn-2877.002.patch, YARN-2882-yarn-2877.003.patch, yarn-2882.patch
>
>
> This JIRA introduces the notion of container types.
> We propose two initial types of containers: guaranteed-start and queueable 
> containers.
> Guaranteed-start are the existing containers, which are allocated by the 
> central RM and are instantaneously started, once allocated.
> Queueable is a new type of container, which allows containers to be queued in 
> the NM, thus their execution may be arbitrarily delayed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to