Return-Path: X-Original-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C330C188CD for ; Fri, 25 Dec 2015 22:34:50 +0000 (UTC) Received: (qmail 82051 invoked by uid 500); 25 Dec 2015 22:34:50 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 81990 invoked by uid 500); 25 Dec 2015 22:34:50 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: yarn-issues@hadoop.apache.org Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 81979 invoked by uid 99); 25 Dec 2015 22:34:50 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 Dec 2015 22:34:50 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id AD59C2C1F5A for ; Fri, 25 Dec 2015 22:34:49 +0000 (UTC) Date: Fri, 25 Dec 2015 22:34:49 +0000 (UTC) From: "Karthik Kambatla (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-4335) Allow ResourceRequests to specify ExecutionType of a request ask MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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)