[
https://issues.apache.org/jira/browse/YARN-2882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15059303#comment-15059303
]
Wangda Tan commented on YARN-2882:
----------------------------------
[~kkaranasos], I think semantic of queueable and opportunistic are very close:
- Both are related to resource overcommitment. (Additional resource to
application)
- Container with either flag could be killed without notice when any of
"guaranteed" container cannot be launched.
- When distributed scheduling is disabled, "queueable" container will be
directly sent to central RM, when LocalRM is enabled, we could have policy to
decide if a queueable request should be sent to central RM. In another word,
end user should be agnostic to if distributed scheduling is involved or not.
Regarding to "execution type" and "container type", I would say "execution
type" is actually affecting how we allocate container as well. Not sure if it's
precise enough.
> 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)
