hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konstantinos Karanasos (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-2882) Add ExecutionType to denote if a container execution is GUARANTEED or QUEUEABLE
Date Wed, 16 Dec 2015 00:54:46 GMT

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

Konstantinos Karanasos commented on YARN-2882:
----------------------------------------------

Thank you for the feedback, [~kasha]. Some comments below:
bq. 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.
Looking into YARN-1011, I also think we should differentiate QUEUEABLE containers from OPPORTUNISTIC
ones. 
QUEUEABLE containers denote that those containers can be queued in the NM until resources
become available, whereas OPPORTUNISTIC are related to the over-commitment of resources at
that NM (correct me if I'm wrong). In that case, OPPORTUNISTIC should probably become an additional
execution type.

bq. 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.
Agreed. [~subru] also pointed out that having the execution type in the ContainerContext will
also be needed for the Timeline Service (this is the reason the ContainerType was also included
in the ContainerContext). Thus, I think we should keep it in the current patch.

bq. 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?
Agreed about pushing it to trunk. I will shortly upload a new patch with some small fixes.

[~leftnoteasy], I propose to keep the ExecutionType naming for the GUARANTEED/QUEUEABLE/OPPORTUNISTIC
containers, since it is more related to the execution rather than the container per se.
However, I agree that probably we should turn the ContainerType to a boolean, if we cannot
think of any other "container type".

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

Mime
View raw message