Konstantinos Karanasos commented on YARN-2882:

Thanks for the feedback, [~leftnoteasy]:

bq. How about renaming ExecutionType to guaranteed/opportunistic 
We opted for queueable instead of opportunistic, since queueable is more 
descriptive and shows better the semantics. If you think queueable is a bad 
name, we could change it back to opportunistic.
bq. Is it necessary to put ExecutionType to ContainerStatus?
It is important to put ExecutionType in the ContainerStatus, because this way 
the RM can differentiate between the different container/execution types. For 
instance, it should not account for resources that are due to queueable 
containers. This way less changes will be required by the AM that will not 
require to keep track of which containers are guaranteed and which are 
bq. Why need to add ExecutionType to 
Agreed. Even if it is needed in the future, you are right that it should not be 
part of this patch, so I will go ahead and remove it.

> 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.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