hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karthik Kambatla (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-4335) Allow ResourceRequests to specify ExecutionType of a request ask
Date Fri, 25 Dec 2015 22:34:49 GMT

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

Karthik Kambatla commented on YARN-4335:
----------------------------------------

My impression from the offline conversation was the AMs should not need to request a specific
ExecutionType. Would like to understand this better: are there any prerequisites for a container
to be executed opportunistically? Are there applications that favor guaranteed vs opportunistic
execution, and is that bias justified? 

In any case, let us drive YARN-2882 to resolution while we figure these things out. 

> Allow ResourceRequests to specify ExecutionType of a request ask
> ----------------------------------------------------------------
>
>                 Key: YARN-4335
>                 URL: https://issues.apache.org/jira/browse/YARN-4335
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: nodemanager, resourcemanager
>            Reporter: Konstantinos Karanasos
>            Assignee: Konstantinos Karanasos
>         Attachments: YARN-4335-yarn-2877.001.patch
>
>
> YARN-2882 introduced container types that are internal (not user-facing) and are used
by the ContainerManager during execution at the NM.
> With this JIRA we are introducing (user-facing) resource request types that are used
by the AM to specify the type of the ResourceRequest.
> We will initially support two resource request types: CONSERVATIVE and OPTIMISTIC.
> CONSERVATIVE resource requests will be handed internally to containers of GUARANTEED
type, whereas OPTIMISTIC resource requests will be handed to QUEUEABLE containers.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message