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 01:51:46 GMT

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

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

bq. I would prefer the above proposal. Overcommitment/queueable are two different just approaches
to handle "extra" allocated containers.
Makes sense. But what if someone wants to allow overcommitment of resources but not queueing
of tasks at the NMs?

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

Mime
View raw message