[
https://issues.apache.org/jira/browse/YARN-2882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15045943#comment-15045943
]
Wangda Tan commented on YARN-2882:
----------------------------------
[~asuresh], sorry for my late response, few comments:
1) How about renaming ExecutionType to guaranteed/opportunistic, I found in
early proposal it is called "opportunistic", not sure why now it is renamed
"queueable"
2) Is it necessary to put ExecutionType to ContainerStatus? We can assume AM
knows containers' executionTypes.
3) Why need to add ExecutionType to
ContainerInitializationContext/ContainerTerminationContext? Should we assume
ExecutionType will be only used by YARN services?
cc: [~curino]
> 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)
