Karthik Kambatla commented on YARN-2882:

Synced up with [~asuresh], [~kkaranasos] and [~subru] offline on this to 
discuss the commonalities with YARN-1011.

The notion of *opportunistic* containers is common, and is governed by the 
following semantics:
# A trusted external agent (RM or LocalRM or NM) can initiate/approve running 
an opportunistic container. 
# 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.
# Only the RM can approve the promotion of an OPPORTUNISTIC container to a 
GUARANTEED container. In case YARN-1011, the RM instigates this directly. 

Haven't looked at the patch closely enough, but high-level comments:
# Since a GUARANTEED container may be preempted, how about calling it REGULAR 
# The ExecutionType is something Yarn decides on. Don't think the client API 
should include it. 

> 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.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