Wangda Tan commented on YARN-2882:

[~kasha], [~asuresh].

For the summary you posted: 

I agree with removing ExecutionType from client API, and also:
bq. Additional policies on execution - queueable or over-subscription - is 
determined by the node's configuration. YARN-2877 would add the queueable flag 
and logic. YARN-1011 would add the over-subscription flag and logic. This logic 
may include having to monitor the usage of the node.

However, I think we still need a flag in ResourceRequest to describe if it's a 
"opportunistic" container or not, correct? Otherwise RM/LocalRM cannot decide 
if it can take risk to allocate a queueable/oversubscribe container.


> Add ExecutionType to denote if a container execution is GUARANTEED or 
> -----------------------------------------------------------------------------------
>                 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-yarn-2877.004.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

Reply via email to