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

Wangda Tan commented on YARN-2882:
----------------------------------

Hi [~asuresh],

Thanks for answering my question , but I still may not understand correctly:
- If opportunistic/guaranteed is solely decided by scheduler, is it possible 
that AM cannot get container in predictable behavior? For example, LRS 
container will be guaranteed only. Another example is MR job want to 
speculative tasks to be opportunistic only.
- Why add limitation to AMs that can only allocate for opportunistic resources. 
(your 2nd point). 

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

Reply via email to