[
https://issues.apache.org/jira/browse/YARN-2882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15071750#comment-15071750
]
Karthik Kambatla commented on YARN-2882:
----------------------------------------
[~asuresh], [~leftnoteasy] - We should probably move the discussion on whether
to expose execution-type in ResourceRequest to YARN-4335. I would like for us
to drive this JIRA to resolution irrespective.
Comments on the latest patch:
# Since we plan to commit this patch to trunk, let us avoid putting yarn-2877
in the branch name and let Jenkins run it against trunk.
# ExecutionType: let us mark it @Evolving as well
# yarn_security_token.proto: define a default value for execution type?
# Looks like there are changes both on NM and RM - did we consider rolling
upgrades here?
# ContainerContext - instead of modifying existing methods' arguments, add a
new method. That way, we can avoid changes to ContainerInitializationContext,
ContainerTerminationContext and other dependent changes. I understand we might
have to handle initialization and termination of opportunistic containers
differently, but let us add the necessary APIs when we need them.
## Update ContainerInitializationContext and ContainerTerminationContext
accordingly.
# Same for ContainerStatus and ContainerTokenIdentifier
[~kkaranasos] - if you are otherwise caught up (holidays), I am happy to post
the patch with the changes and [~asuresh] could review.
> Add ExecutionType to denote if a container execution is GUARANTEED or
> OPPORTUNISTIC
> -----------------------------------------------------------------------------------
>
> Key: YARN-2882
> URL: https://issues.apache.org/jira/browse/YARN-2882
> Project: Hadoop YARN
> Issue Type: New Feature
> Components: nodemanager
> 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-yarn-2877.004.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)
