Arun Suresh commented on YARN-2882:

Hey [~leftnoteasy],

bq. If opportunistic/guaranteed is solely decided by scheduler..
So, it neednt be decided solely by the Scheduler. Taking into consideration 
YARN-1011, if oversubscription is required, yes, this will be decided by the 
Scheduler, else if the NM is configured to support Distributed Scheduling, this 
decision can be made by the LocalScheduler, or via the application of a Policy 
(just created YARN-4503 to track this)

bq. is it possible that AM cannot get container in predictable behavior?
If the above mentioned policy makes the decision on static parameters such as 
locality or container size etc, yes, it should be consistent.. if it is more 
dynamic, for eg. based on load etc, then not so much... but we feel AM should 
not need to know.

bq. Why add limitation to AMs that can only allocate for opportunistic 
Apologize if I wasnt clear. what I meant was this : If an AM is not able to 
specifying the type of resource request.. then we can also ensure that 
mis-behaving AMs wont flood the scheduler with only GUARANTEED requests.

> Add ExecutionType to denote if a container execution is GUARANTEED or 
> -----------------------------------------------------------------------------------
>                 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

Reply via email to