Karthik Kambatla commented on YARN-2882:

In YARN-1011, we plan to allocate resources based on utilization. We need a 
similar differentiation - guaranteed and opportunistic. If the guaranteed 
containers end up using all allocated resources, the opportunistic containers 
are to be preempted. For this preemption, we might want to set cgroups and OOM 
Killer priorities for these opportunistic containers differently. 

# Do the opportunistic containers in YARN-1011 and here share characteristics 
enough to be the same? If yes, can we call them opportunistic instead of 
queueable. Otherwise, we are probably better off calling them queueable. 
# To set the cgroups and OOM priorities, we need the type in container 
initialization context. I am fine with adding it in this patch or later. 
# We are considering developing YARN-1011 also on a branch. Any ideas on how we 
can share code? May be, deliberate more on the container execution type and 
commit it to trunk itself? 

I would like to do a more thorough review of the patch here once we finalize on 
these items and I am more awake :)

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