[
https://issues.apache.org/jira/browse/YARN-2882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15059434#comment-15059434
]
Arun Suresh commented on YARN-2882:
-----------------------------------
I was giving this some thought.. I feel that both solutions proposed above viz.
# adding both OPPORTUNISTIC / SPECULATIVE and QUEUEABLE
# overloading OPPORTUNISTIC and using a boolean to specify distributed /
centralized scheduling
is adding extra burden on the AM to qualify a request ask. A decision, which I
don't think most AMs might be equipped to make.
I feel an AM must just mark its essential request asks as GUARANTEED.. and the
NM via some config / policy should decided how to handle non-guaranteed asks..
which might result in couple of outcomes :
# make the *Distributed Scheduling* and *Opportunistic Central scheduling*
mutually exclusive (only 1 can be enabled)
# allow the LocalRM to handle some of the non-guaranteed asks and route rest to
the RM Scheduler
etc.
which brings me to wonder... why cant we just have Execution type as a boolean,
maybe name it *isGuaranteedAsk* ? and like [~leftnoteasy] suggested, rename
ContainerType to *isAMContainer*.
Of course this would mean giving the AM a little less control on the container
launch guarantees if the value is set to false.
> 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-yarn-2877.003.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)
